Skip to main content
Glama

Read one public page's framing

get_public_page
Read-onlyIdempotent

One public page as written: its heading, its lead, and the sections it carries — what the page says it does, what it covers, and what it does not. This returns copy, not a run: the tools on these pages compute from a reader's own answers, and nothing here invents one. Routes: /tools, /first-pass, /deal-ready-ai, /roadmap, /data, /second-opinion, /compute, /build, /agents, /tools/mcp.

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": {
      "page": "<page>"
    },
    "name": "get_public_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe page's route, as list_public_pages gives it: /tools, /first-pass, /deal-ready-ai, /roadmap, /data, /second-opinion, /compute, /build, /agents, /tools/mcp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds genuinely new behavior: this fetches static copy and performs no computation, and 'nothing here invents' a reader's answers. That is meaningful context for an agent that might otherwise expect the page's tools to be executed. It stops short of describing size, truncation, or the shape of the 'sections' payload.

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?

The purpose is front-loaded in the first clause and the key disambiguation ('returns copy, not a run') follows immediately. The closing route list is redundant with the schema enum and could be dropped without loss, which is the only real waste.

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

Completeness5/5

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

With no output schema, the description carries the return-shape burden and does so — heading, lead, and sections explicitly described, plus a clarification that no computation occurs. For a single-enum-parameter read tool this is complete enough to call correctly.

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 single parameter is enum-constrained with a full list, so the schema does the heavy lifting. The description's trailing route enumeration merely repeats that enum rather than adding semantics such as what each route covers or what happens with malformed routes. Baseline 3 applies.

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 names a specific resource and scope — 'one public page as written' with 'its heading, its lead, and the sections it carries' — which lets an agent distinguish it from the listing sibling implied by the schema wording 'as list_public_pages gives it.' It also distinguishes itself from the computation tools by saying it 'returns copy, not a run,' though the verb is implied rather than stated outright.

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?

Usage is implied rather than stated: the agent can infer this is the single-page read companion to list_public_pages, and learns it is not the tool for computed output. There is no explicit 'use this when X, use that when Y' routing statement naming an alternative, so the agent must reconstruct the split from the schema and description.

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