Skip to main content
Glama

Get Indicator History

get_indicator_history
Read-onlyIdempotent

Retrieve published values for a Mexican economic indicator (FIX, UDIS, TIIE, CCP) across a chosen date range of up to 400 days to analyze historical trends.

Instructions

Get the published values of one indicator over a date range (up to 400 days).

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": {
      "indicator": "<indicator>"
    },
    "name": "get_indicator_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNoEnd date (inclusive). Defaults to today.
date_fromNoStart date (inclusive). Defaults to 30 days before date_to.
indicatorYesusd (FIX exchange rate), udis, tiie28, tiie91, tiie182, tiie_fondeo, cpp, ccp, ccp_udis or ccp_usd.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency are covered. The description adds a genuinely behavioral fact, the 400-day maximum window, but does not say whether exceeding it errors or truncates, nor whether results are paginated.

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?

One sentence, front-loaded with the verb and resource, with the window limit in parentheses. Nothing is superfluous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and all parameters are documented, so the description's burden is light. However, the accepted date string format is unspecified in both schema and description, and the consequence of exceeding the 400-day cap is unstated, which is material for a range-based tool.

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 would be 3, but the description contributes a cross-parameter constraint (the combined date_from/date_to span may not exceed 400 days) that the schema cannot express. It does not add date-format syntax beyond what the schema implies.

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 ('Get'), a precise resource ('published values of one indicator'), and a scope ('over a date range'). The word 'one' implicitly separates it from the sibling 'get_indicators', though no sibling is named 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 implied rather than stated: an agent can infer this is for a single-indicator time series, while 'get_indicators' presumably handles multiple. No explicit when-to-use, when-not, or named alternative is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.