Skip to main content
Glama

Get a number

get_number
Read-only

One number's current value with its date, the page it was read from, when it last changed and by how much, and where its history and chart are. Cite the 'page' address when you use the value.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe number's id, from search_numbers.
pageNoOr the number's page address on tallycatalog.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully discloses the shape of the returned payload (value, date, source page, last change and delta, links to history and chart), which is valuable given no output schema, but it says nothing about behavior on an unknown id or when both optional parameters are omitted.

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

Conciseness4/5

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

Two sentences, no filler, with the payload contents front-loaded and the citation requirement last. The first sentence is a long comma-chained list but remains readable.

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 simple read-only lookup with no output schema, the description covers the returned fields and one important downstream behavior (cite the page). The remaining gap is the absence of any statement about error or empty-parameter behavior for a tool with zero required parameters.

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%, so both parameters are already documented, including the reference to search_numbers for ids. The description only reinforces the 'page' concept via 'the page it was read from' and the citation instruction; it adds no new semantics such as precedence between id and page.

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 retrieval action and resource ('One number's current value') and enumerates what the response carries (date, page, last change, delta, history/chart locations). It implicitly distinguishes itself from search_numbers by scoping to a single number, though it never names the sibling explicitly.

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: fetch details for one already-known number, and 'where its history and chart are' hints that history lives elsewhere. There is no explicit statement of when to prefer this over search_numbers or get_history, and no guidance for the case where neither identifier is supplied.

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.