Skip to main content
Glama

read_page

Read-onlyIdempotent

Lees één publieke pagina uit deze build. Geef een exact canoniek adres uit search_content. Haalt geen externe URL op en kan geen aanvragen of accounts lezen.

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": {
      "url": "<url>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false. The description reinforces the closed-world scope and adds a non-obvious limitation beyond the annotations — it cannot read requests or accounts — which tells the agent what content classes are out of reach. It does not describe the returned page's shape, which holds it back from a 5.

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

Conciseness5/5

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

Three short sentences with no filler. Scope comes first, then the parameter prerequisite, then the exclusions — a well front-loaded order for an agent scanning before a call.

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 one-parameter read tool with annotations covering safety and no output schema, the definition supplies purpose, input provenance and scope limits. The remaining gap is return behavior — what the page content looks like and whether it is truncated — which is not covered by any output schema and is left unstated.

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

Parameters4/5

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

Schema description coverage is 0% (only type/format/maxLength), so the description must carry the meaning, and it does: the parameter is an exact canonical address, not an arbitrary link, and its provenance is search_content. It could have added an example format or said what happens on a non-canonical input.

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?

The description states a specific verb plus resource: read ONE public page from this build. It narrows scope on three axes (single page, public, within this build) and contrasts with the sibling by requiring the address to come from search_content, so an agent can tell it apart from search_content without opening 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?

It gives a clear prerequisite and routing rule: the url argument must be an exact canonical address obtained from search_content, and external URLs are out of bounds. It stops short of an explicit when-not-to-use list, but the sourcing constraint and the external-URL exclusion together cover the realistic misuse cases.

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