Skip to main content
Glama

Read a public site document

read_public_page
Read-only

Read the full Markdown text of a named public page on richsteinmetz.com. Use this to answer a question with the site’s exact language or to retrieve a source URL for a citation.

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": "<page>"
    },
    "name": "read_public_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesChoose home for consulting, about for Rich’s background, contact for inquiries, docs for the public API and MCP guide, pricing for the call and project pricing, privacy for data handling, or terms for call and site terms.

Output Schema

NameRequiredDescriptionDefault
uriYesCanonical URL of the Markdown document.
pageYesShort name of the public page.
markdownYesFull text of the Markdown document.
mimeTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavioral context by saying it returns full Markdown text and can provide a source URL, but it does not discuss permissions, errors, or other operational details.

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?

The description is two sentences, front-loaded with the core action and followed by the primary use cases. Every sentence contributes useful information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple one-parameter read operation, existing annotations, rich enum schema, and output schema, the description is complete enough for an agent to select and invoke the tool correctly. It covers purpose, usage context, and return content without needing to restate schema details.

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 description coverage is 100%, and the single page parameter has a detailed enum description explaining each allowed value. The description adds no parameter meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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: reading the full Markdown text of a named public page on richsteinmetz.com. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling tools get_consulting_overview and get_solution_definition_call.

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?

It gives clear usage contexts: answering a question with the site’s exact language or retrieving a source URL for citation. It does not state when not to use it or name alternatives, so it falls short of full when/when-not guidance.

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