docs: Tweaked MCP docs on capability listing

2026-08-28 11:38:51 -06:00
parent 4762748875
commit 0ba1a0603d
+3 -3
@@ -799,10 +799,10 @@ tools (2 allowed / 4 total)
* ✓ rows show which pattern matched in each layer, joined with `∧`.
* ✗ rows name the first layer that hid the tool.
* The `capabilities` line live-probes prompts and resources: capabilities with served items show a count (e.g.
`prompts (2)`, `resources (3)` resources count includes templates), while a capability the server declares but
serves nothing for is omitted entirely — some SDKs advertise prompts/resources unconditionally, and a capability
`prompts (2)`, `resources (3)`, resources count includes templates), while a capability the server declares but
serves nothing for is omitted entirely. Some SDKs advertise prompts/resources unconditionally, and a capability
with zero items is not worth listing. If a probe errors, the capability can't be proven empty and is shown as
`prompts (declared, list failed)`. `tools` is never annotated the tool table below it tells the full story.
`prompts (declared, list failed)`. `tools` is never annotated; the tool table below it tells the full story.
* ⚠ lines flag **dead patterns**: patterns that match none of the server's allowed tools (usually typos). Dead
patterns are also logged as warnings when the server's catalog is fetched.
* With no active filter, the header shows `filter layers (none — all tools allowed)` and every tool is a bare ✓.