Skip to main content
Glama

Get a number's history

get_history
Read-only

The dated past values of one number, oldest first, each with the page it was read from. Use it for trends, growth rates and 'what was it on a given date'.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe number's id, from search_numbers.
pageNoOr the number's page address on tallycatalog.com.
limitNoHow many of the latest points to return (default 200, at most 1000).
sinceNoOnly values on or after this date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 adds genuinely useful return-shape detail, namely oldest-first ordering and a source page per point, which matters because there is no output schema. It says nothing, though, about what happens when neither identifier is supplied or how the alternative id/page params interact.

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 tight sentences with no filler, and the return characteristics are front-loaded before the usage advice.

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 four-optional-parameter read with full schema coverage, the description plus schema covers nearly everything an agent needs. The only real gap is the zero-required-parameter design: it never states what happens if neither id nor page is provided.

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%, so all four parameters are already documented, including default and max for limit and the YYYY-MM-DD format for since. The description adds only the notion of 'one number' being addressed, without clarifying the id-versus-page choice or what the default is when neither is given.

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 names a specific resource and verb: the dated past values of one number, returned oldest first. It implicitly distinguishes itself from the sibling get_number by emphasizing history rather than a current value, though it never names that 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete use cases (trends, growth rates, 'what was it on a given date') that tell the agent when this tool fits. It stops short of explicit exclusions or naming an alternative tool for current-value lookups.

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.