fix(docs): Docs MCP available-tools table lists an unexposed get_page_x tool #504

Summary

The Docs MCP “Available tools” table lists get_page_x for retrieving a complete documentation page, but the hosted server's complete tool discovery response does not expose that name. A client implementing the documented page-retrieval workflow cannot select that tool from discovery.

Runtime or environment

The current default branch was inspected at 5fcfe3da51461ef1c0b59a028da9c365547cad4c. The hosted Docs MCP reported server name X, server version 1.0.0, and protocol 2025-06-18; requests used Streamable HTTP without authentication. The repository has no published GitHub releases. The deployed Markdown guide also contains the same table.

Steps to reproduce

1. Read tools/mcp.mdx, under “Docs MCP — documentation search” → “Available tools.”
2. Run this read-only discovery request; it requires no credentials:

curl -sS \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' \
  https://docs.x.com/mcp

3. Inspect result.tools[].name in the JSON-RPC response, which may be carried in an SSE data: event. Check whether pagination requires another request.

Both discovery following an initialize handshake and the direct request above were executed. No documentation tool was called.

Expected behavior

The table's available-tool names should match tools exposed by the hosted server, and the documented complete-page retrieval tool should be discoverable if the guide presents it as available.

Actual behavior

The server returned exactly these three tools, with no nextCursor:

search_x
query_docs_filesystem_x
submit_feedback

get_page_x was absent in both discovery requests. The table lists search_x and get_page_x instead.

Evidence

• Expected source: the Docs MCP available-tools table.
• Failure source: The unauthenticated hosted discovery responses summarized under Actual behavior, including a complete response without a pagination cursor.
• Evidence provenance: observed
• Local verification: reproduced
• Reproduction completeness: complete

Restoration check

Repeat discovery against the documented server and compare its complete exposed tool set with the table. The failing signal is the table naming an unavailable get_page_x; a passing result provides accurate available-tool names and an accurate statement of the supported complete-page retrieval workflow, without assuming an undocumented replacement is equivalent.

Triage assessment

• Impact level: P2
• Assessment status: supported
• Impact basis: The table directs clients toward a tool that is absent from complete discovery, preventing selection of the documented tool for complete-page retrieval; this is bounded to that documented workflow.
• Workaround status: unverified
• Workaround basis: Discovery exposes other tools, but this check did not invoke them to establish an equivalent complete-page retrieval path.