Skip to main content
Glama

The Meaning of Numbers

get_site_guide

Read-onlyIdempotent

Return when-to-use guidance for The Meaning of Numbers: free vs paid, Markdown twins, and honest auth limits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_site_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds only mild context ('honest auth limits'), signaling that auth constraints are documented inside the guide, but says nothing about size, format, or freshness of the returned guidance beyond what the output schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is good. The cost is that its compactness relies on insider jargon ('Markdown twins', 'The Meaning of Numbers') that an unfamiliar agent cannot decode, so efficiency trades against clarity.

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 zero-parameter, read-only guide tool with an output schema, the description covers enough: what the guide contains and that auth limits are included. The remaining gap is guidance on when to reach for this versus ask_site, which would complete the picture.

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?

There are zero parameters, so the baseline is 4; the description correctly implies no input is required to fetch the guide. Nothing about parameter behavior is misrepresented or missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and artifact ('Return when-to-use guidance') and lists covered topics: free vs paid, Markdown variants, and auth limits. However, phrases like 'The Meaning of Numbers' and 'Markdown twins' are opaque to an outside agent, and no sibling is named to sharpen the boundary with ask_site. The purpose is inferable but not crisp.

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 content implies this tool should be consulted to learn which mode/tool to use (free vs paid, Markdown alternatives, auth limits), giving implied usage. It never states explicitly when to call this before or instead of siblings like ask_site or get_page_markdown, leaving routing to inference.

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