get_doc_pageReturn one page of agent-manager.dev as Markdown, with the site chrome removed. The slug comes from search_docs or list_doc_pages and may contain slashes.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Page slug, for example install, mcp, or writing/live-review-race. |
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| slug | Yes | ||
| title | Yes | ||
| section | No | ||
| markdown | Yes | ||
| description | No | ||
| markdown_url | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so no safety concern is hidden. The description adds useful behavioral context beyond the annotations: output is Markdown and the site chrome is removed. It does not describe error behavior for invalid slugs, but the presence of an output schema reduces the need for that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The core behavior is stated first, and the second sentence adds only the input-origin detail that is genuinely useful. Every phrase earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, read-only tool with a rich output schema and sibling tools, this description is complete. It tells the agent what the tool returns, the input source, and the formatting behavior. Nothing essential is missing for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the slug parameter with an example and minLength. The description adds meaningful extra context by explaining that the slug comes from search_docs or list_doc_pages and may contain slashes, which helps the agent understand valid inputs and how to generate them.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific action ('Return one page'), a specific resource ('agent-manager.dev'), and the output format ('Markdown'). It clearly differentiates from sibling tools like list_doc_pages and search_docs, which are for discovery rather than fetching a single page.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells the agent that the slug comes from search_docs or list_doc_pages, providing clear guidance on how to obtain a valid input. It does not explicitly state when not to use this tool, but the phrase 'one page' plus the named alternatives make the intended usage context clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct role: listing all docs, searching docs, fetching one doc page, retrieving the latest release, listing managed MCP tools, and listing supported agents. The two product-listing tools are separated by subject matter, and the three documentation tools form an obvious search-list-read flow.
All tool names follow the same lowercase verb_noun pattern: get_, list_, and search_. Multi-word targets like managed_mcp_tools and supported_agents are consistently underscore-separated and readable. There are no mixed conventions or vague action verbs.
Six tools is well-scoped for a documentation and product-information server. It provides enough surface to discover, search, and read documentation while also covering release and compatibility information, without redundant or marginal tools.
The surface covers the complete read-only documetation lifecycle: inventory via list_doc_pages, discovery via search_docs, and content via get_doc_page. It also answers likely product questions about releases and supported agents, with search and list flows feeding directly into page retrieval. No create/upate/delete operations are expected for a docs server.