From 0ba1a0603d01509d205bbf334a00a2212fe72916 Mon Sep 17 00:00:00 2001 From: Alex Clarke Date: Fri, 28 Aug 2026 11:38:51 -0600 Subject: [PATCH] docs: Tweaked MCP docs on capability listing --- MCP-Servers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/MCP-Servers.md b/MCP-Servers.md index 044d509..aa0f90f 100644 --- a/MCP-Servers.md +++ b/MCP-Servers.md @@ -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 ✓.