Skip to main content
Glama

The Meaning of Numbers

get_page_markdown

Read-onlyIdempotent

Fetch the Markdown twin for a public path (for example /angel-numbers/444 or /). Returns 404 text for unknown paths.

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_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesSite path beginning with /

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so the safety profile is covered. The description adds genuinely useful behavior beyond that: unknown paths return 404 text rather than an error, and only public paths are served. It omits auth or rate-limit considerations, which is a minor gap.

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 short sentences, front-loaded with the core action and followed immediately by the failure-mode note. No filler, and the examples are placed where they are most useful.

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?

With an output schema present, the description need not explain return values, and it correctly focuses on the one thing the schema cannot express: 404 text for unknown paths. For a one-parameter read tool this is nearly complete, with only public-vs-private access rules left implicit.

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% and the single parameter is already documented as "Site path beginning with /". The description reinforces this with example paths (/angel-numbers/444 and /), which adds modest clarity but no new semantics beyond what the schema provides.

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 ("Fetch") and resource ("the Markdown twin" of a page), plus concrete path examples that make the concept concrete. It is clearly distinct from siblings like ask_site and calculate_core_numbers, though it never explicitly contrasts itself with get_site_guide.

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?

Usage is only implied: the tool retrieves raw Markdown for a public path, so an agent can infer it should be used when raw page content is needed rather than a guide or answer. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative.

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