Skip to main content
Glama

Read a page as Markdown

get_page
Read-onlyIdempotent

The full text of one public page as Markdown, by its path: "/" (home), "/about", "/process", "/faq", "/awards", "/work/", "/news/" and so on. Use it after search_site or list_work to read and cite the page itself.

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": {
      "path": "<path>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe page path, starting with "/", e.g. "/about" or "/work/<slug>".

Output Schema

NameRequiredDescriptionDefault
urlYes
pathYes
markdownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the description only needs to add context — and it does, by scoping retrievable content to "public" pages and specifying that the whole page text comes back. It does not cover failure behavior for unknown or non-public paths, which keeps it below a 5 given rich annotations already carry the safety profile.

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?

Two sentences, front-loaded with what is returned and keyed by path, with the usage hint second. The path enumeration is dense but each entry is an example an agent can act on; a trimmer list would lose little, which is the only thing keeping this from a 5.

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?

This is a single-parameter read tool with an output schema, so return values need not be explained, and the description covers what is fetched, from where, and in what sequence. The remaining gap — what happens when a path does not exist or is not public — is minor for a simple idempotent read.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it enumerates the site's actual path space ("/" as home, "/process", "/faq", "/awards", "/news/<slug>") where the schema only shows two illustrative examples. This tells an agent which paths are plausible inputs rather than just the string format.

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 full text of one public page as Markdown, by its path" gives a specific verb (read), a bounded resource (one public page), and an output format (Markdown). A single page read is cleanly distinguishable from sibling list/search tools like list_work and search_site.

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 it after search_site or list_work to read and cite the page itself" explicitly names the alternatives and the sequencing that selects this tool over them. It stops short of stating when not to use it (e.g., that it cannot enumerate or filter pages), so it is clear but not exhaustive.

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