Skip to main content
Glama

NS Pros MCP Gateway

aws-mcp__aws___read_documentation

Fetch full AWS doc pages as markdown. search_documentation already returns verbatim page chunks, so don't re-read a URL whose chunk you already have to "confirm" or "round out" an answer -- the chunk is the real page text; treat it as authoritative.

Reading the full page is justified ONLY when the chunks genuinely lack the content:

  • an enumeration or aggregation ("list all X", "how many X") needs the complete set and the chunks show only part of it;

  • no search result is on-topic after refin

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aws-mcp__aws___read_documentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestsNoList of `{url, max_length?, start_index?}`. Batch 2-5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it declares the return medium (markdown), asserts that search chunks are verbatim page text, explains pagination continuation via `end_index` and TOC offsets, and notes the allow-listed URL prefix constraint. It does not cover auth requirements, rate limits, or failure modes for non-allow-listed URLs, so it is not exhaustive.

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?

Front-loads the core action, then moves to the anti-pattern warning and the justification list in a scannable order. The scare-quoted 'confirm'/'round out' phrasing is slightly chatty, but every sentence carries a distinct decision rule.

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

Completeness3/5

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

For a single-optional-parameter read tool with no output schema, the description adequately covers what is returned and how to paginate. It omits the practical mechanics an agent would want — how errors surface for disallowed URLs and whether batching interacts with pagination — leaving the definition merely adequate.

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 schema already documents `url`, `max_length`, and `start_index` including defaults and the end_index/TOC continuation rule. The description's only added hint ('use exact URL from search') largely restates the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource — 'Fetch full AWS doc pages as markdown' — and explicitly contrasts it with the sibling `search_documentation`, whose chunked output it says is already authoritative. An agent can tell the two apart without inspecting either schema.

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

Usage Guidelines4/5

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

Gives unusually explicit negative guidance ('don't re-read a URL whose chunk you already have') followed by two positive trigger conditions (enumeration/aggregation needing the complete set, and no on-topic search results). The final bullet is truncated mid-word ('after refin'), so the last condition is left incomplete, which keeps it short of a full 5.

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.