Skip to main content
Glama

Get recorded endpoint history

get_history
Read-onlyIdempotent

Returns change points this service recorded over time for an endpoint (e.g. exchange rates, weather) as compact CSV. Use the same params as the live call. When to use: to see how a live value (e.g. an exchange rate or the weather at a place) changed since this service started recording it. For long official histories use get_series instead. Returns an error if nothing was recorded for these params. Read-only, no API key or signup. Free quota: 1000 calls/day per IP, shared across tools.

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": {
      "apiId": "<apiId>"
    },
    "name": "get_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoISO date, e.g. 2026-01-01
apiIdYesEndpoint id; list recorded ones via GET /api/v1/history
limitNoMax points (default 200, max 1000)
fieldsNoComma-separated data fields to include
paramsNoSame params as the live call (omit for the default series)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / apiId / description
      Previous value: -"Endpoint ID, see GET /api/v1/history for recorded series"New value: +"Endpoint id; list recorded ones via GET /api/v1/history"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the error case ('Returns an error if nothing was recorded for these params'), the auth profile ('no API key or signup'), and a concrete quota ('1000 calls/day per IP, shared across tools'). These are exactly the operational constraints annotations cannot express.

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?

Four short sentences, front-loaded with the core behavior and return format, then usage, then the alternative, then operational caveats. Every sentence carries distinct, actionable information with no repetition of the title.

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?

For a read-only, five-parameter tool with full schema coverage and no output schema, the description covers return format (CSV), failure mode, auth, quota, and sibling routing. An agent has everything needed to decide to call it and to interpret a likely error.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-tool meaning by telling the agent to reuse the live call's params, which clarifies what the nested `params` object should contain in relation to call_api. It stops short of adding format or defaulting detail beyond what the schema already documents.

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

Purpose5/5

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

States a specific verb and resource ('Returns change points this service recorded over time for an endpoint') with concrete examples (exchange rates, weather) and an output format (compact CSV). It explicitly distinguishes itself from the sibling get_series ('For long official histories use get_series instead') and implicitly from call_api by framing this as the recorded counterpart to the live call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides an explicit 'When to use' clause tied to a recognizable scenario (seeing how a live value changed since recording began) and names the alternative (get_series) with the condition that selects it. Nothing about tool selection is left 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