Skip to main content
Glama

Get hosted page

get-hosted-page
Read-only

Get one hosted page for review: status, body_md, gap_evidence and unverified_claims (the claims a fact check flagged). page_id comes from list-hosted-pages; claim indexes feed dispose-hosted-claim. Requires Lead Pages on the plan.

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_id": "<page_id>"
    },
    "name": "get-hosted-page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesHosted page ID from list-hosted-pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page_id / description
      Previous value: -"Hosted page ID"New value: +"Hosted page ID from list-hosted-pages"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the exact payload fields returned, that unverified_claims are fact-check flags, and the 'Requires Lead Pages on the plan' entitlement gate, which is a failure mode an agent otherwise wouldn't anticipate.

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?

Front-loaded with the verb and the returned fields, then workflow pointers and the plan gate in short clauses. No filler sentences; every clause carries information.

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?

With no output schema, the description does the work of naming the returned fields and their meaning, and it flags the plan requirement. Minor gaps remain (behavior on missing/inaccessible page_id, whether body_md is raw markdown), but an agent has what it needs to call it 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 coverage is 100% and the single page_id parameter is already documented as coming from list-hosted-pages, so the description largely repeats the schema. It adds only the downstream link that claim indexes from this response feed dispose-hosted-claim, which is marginal added meaning for a one-parameter tool.

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 (get one hosted page) and enumerates what comes back: status, body_md, gap_evidence, unverified_claims. It is clearly distinguishable from list-hosted-pages, which is named as the source of page_id.

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 the operating context ('for review'), the predecessor ('page_id comes from list-hosted-pages'), and the downstream consumer ('claim indexes feed dispose-hosted-claim'), plus a plan prerequisite. It stops short of stating when not to use it, but the workflow placement is unambiguous.

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