Skip to main content
Glama

Read a page as markdown

read_page
Read-only

Read any page of status403 as markdown: "/" for the homepage (services, process, booking, FAQ), "/blog" for the post index, or "/blog/" for a post in full. This is the same document the site serves to clients that ask for it with Accept: text/markdown.

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": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesSite path, such as "/" or "/blog/<slug>". A full status403.com URL works too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's job is lighter. The note that the result is "the same document the site serves to clients that ask for it with `Accept: text/markdown`" usefully establishes that the markdown is the canonical rendered document, but nothing is said about behavior on an invalid path, response size, or whether the full post is truncated.

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?

Two sentences, front-loaded with the core action, then the path map, then a single clarifying detail about content fidelity. Nothing is redundant or padded.

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 one-parameter read-only tool with no output schema, the definition covers the action, the valid inputs, and what kind of document comes back. It could say slightly more about error behavior for unknown paths, but nothing essential for correct invocation is missing.

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% and the schema already states the path format and that full URLs work. The description still adds meaning by mapping each path to the content it returns (homepage covers services, process, booking, FAQ; /blog is the index; /blog/<slug> is a full post), which the schema does not convey.

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?

"Read any page of status403 as markdown" gives a specific verb and resource, and the route enumeration ("\"\" for the homepage, \"/blog\" for the post index, \"/blog/<slug>\" for a post in full") pins down exactly what 'page' means. It implicitly separates raw-document retrieval from the sibling tools (search_blog, list_services) but never names them, so it stops short of a 5.

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?

The description gives clear path-selection guidance (which path yields which content), but that is usage of the parameter rather than usage of the tool. It never says when to reach for this instead of search_blog or answer_common_question, and gives no exclusions.

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