Skip to main content
Glama

Get Page

get_page
Read-onlyIdempotent

Get the full content of a specific page, including all its blocks. Use page slugs from get_site.

Annotations: read-only=true, destructive=false, idempotent=true, open-world=false. Why: Reads data only and changes nothing (read-only, so trivially idempotent). Closed-world: it touches only Zarla's own database.

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_id": "<site_id>",
      "page_slug": "<page_slug>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site ID
page_slugYesPage slug (e.g., "/", "/about", "/services/paint-correction")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the annotation block itself explains the rationale, so the description carries little extra burden. The description contributes only the content-scope note that all blocks are included; it says nothing about size limits, pagination, or error behavior for a missing slug.

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?

A single front-loaded sentence plus a short prerequisite clause; no filler, no restatement of the title, and the most important constraint (slug source) is stated immediately.

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 simple two-parameter read tool with full schema coverage and no output schema, the description covers purpose, content scope, and input provenance. Minor gaps remain around response size and behavior when a slug does not exist, but nothing essential is missing for correct invocation.

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%, so both parameters (site_id and page_slug, including slug examples) are already fully documented in the schema. The description adds only the provenance hint that slugs come from get_site, which is a marginal gain over structured data.

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 states a specific verb and resource ('Get the full content of a specific page') and adds scope detail ('including all its blocks') that goes beyond the bare name. It is clear what the tool returns, though it does not contrast itself with neighboring readers such as get_site beyond naming the slug source.

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?

'Use page slugs from get_site' gives an explicit prerequisite and points the agent to the tool that supplies valid input, which is the main usage risk here. There is no explicit when-not guidance or named alternative for adjacent read needs, so it stops short of a 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.