Skip to main content
Glama

Mike Reams: architecture writing, diagrams and toolbox

Read a page as Markdown

get_page
Read-onlyIdempotent

Read one public page (a post, work item, diagram, skill, /about or /toolbox) as Markdown, with its canonical URL. Pass a path such as /writing/ or a full mikereams.com URL.

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
pathYesPath or https://mikereams.com URL of the page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds scope ('public page' only, hinting non-public paths fail) and the return shape (Markdown plus canonical URL), which the annotations do not provide.

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, no filler, with the read scope and supported page types front-loaded before the parameter usage detail. 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?

For a single-parameter read tool with rich annotations and no output schema, this covers purpose, scope, and input format adequately. It stops short of describing failure behavior for non-public or missing paths, which is the only remaining gap.

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 there is only one parameter, so the baseline is already a 3. The description adds concrete accepted shapes ('/writing/<slug>' or a full mikereams.com URL) that make the single parameter unambiguous in practice.

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?

States a specific verb and resource ('Read one public page') and enumerates the page kinds it covers (post, work item, diagram, skill, /about, /toolbox) plus the output format (Markdown with canonical URL). The word 'one' implicitly contrasts with the list_* siblings, but no sibling is named, so differentiation is inferred rather than stated.

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 sentence 'Pass a path such as /writing/<slug> or a full mikereams.com URL' is invocation guidance, not when-to-use guidance. An agent can infer this is the fetch-one-known-page tool versus search_site for discovery, but the description never says when not to use it or what to do if the page is unknown.

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