Skip to main content
Glama

Pumpkin

read_site_page

Read-only

Read a published page by its search result id.

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": {
      "site": "<site>",
      "id": "<id>"
    },
    "name": "read_site_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
siteYesThe site ID returned by find_business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is known. The description adds the scope constraint that only 'published' pages are readable, which is useful, but says nothing about return shape, missing/unpublished page behavior, or size limits beyond what the annotations carry.

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?

A single front-loaded sentence with no filler; every word carries information. It is arguably over-terse, but nothing is redundant.

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 two-parameter read tool with rich annotations and no output schema, the essentials are present: what it reads and the origin of the id. What the returned page object contains and what happens for an unpublished or invalid id remain unspecified, which is a meaningful gap for a content-fetch tool.

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 coverage is 50%: 'site' is documented in the schema as a site ID from find_business, while 'id' has only a maxLength. The description partially compensates by clarifying that 'id' is a search result id, but it does not say where 'site' comes from or how the two interact.

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?

States a specific verb ('read') and resource ('published page') and identifies the key ('search result id'), so the agent knows the operation is a by-id fetch. It does not name the sibling that produces those ids (search_site_pages), so differentiation is only implied.

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

Usage Guidelines3/5

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

'by its search result id' implies the caller must first obtain an id from a search, which is the key usage condition. There is no explicit statement of when to use this versus search_site_pages or another lookup, and no exclusion or prerequisite spelled out.

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