Skip to main content
Glama

Read any page of the site

read_page
Read-onlyIdempotent

Any page of anchorterminal.com as Markdown, such as /top/, /categories/search/, /benchmark/ or /agents/.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe page's path on the site, e.g. /top/ or /categories/search/
formatNomarkdown (the default), slim for the fewest tokens, or json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior — the response is Markdown, and the format parameter can trade fidelity for tokens — but says nothing about what happens for an invalid or non-existent path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the resource and the return type, with examples carrying real information rather than filler. Only the missing verb keeps it from reading as a fully self-contained statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with full schema coverage, complete annotations, and no output schema, the description covers the essentials: what resource, what return format, and example paths. Error behavior on bad paths is the only meaningful omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the enum is documented inline, so the baseline is 3. The description reinforces path semantics with four concrete example paths and echoes the Markdown default, but adds no format-selection guidance beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource (any page of anchorterminal.com) and the output form (Markdown), with concrete path examples that make the scope unambiguous. It is an elliptical noun phrase with no verb and never contrasts itself with siblings like get_tool or search_tools, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Any page' implies broad applicability but gives no when-to-use conditions, no prerequisites, and no named alternative for cases better served by get_tool, search_tools, or list_capabilities. The agent must infer routing from sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources