Skip to main content
Glama

DOF financial indicators

dof_get_indicators
Read-onlyIdempotent

Fetches Mexican DOF financial indicators—FIX exchange rate, UDI, and TIIE rates—for today, a given date, or a daily date-range series of up to 366 days.

Instructions

Returns indicators published in the DOF: FIX exchange rate (pesos per dollar), UDI value and TIIE rates. Without arguments, returns what SIDOF lists for today (on weekends and holidays that can be only the UDI). With date, the values published that day. With indicator, from and to, the daily series of one indicator (at most 366 days); prefer a series to find the most recent value of one indicator.

Input Schema

NameRequiredDescriptionDefault
toNoSeries end, YYYY-MM-DD (needs indicator)
dateNoPublication day, YYYY-MM-DD
fromNoSeries start, YYYY-MM-DD (needs indicator)
indicatorNoIndicator for a date-range series

Output Schema

NameRequiredDescriptionDefault
sourceYes
indicatorsYes
provenanceYesSIDOF URL the data came from, fetch time (UTC) and SHA-256 of the raw response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds meaningful operational context beyond that, including the weekend/holiday caveat, the date-publication behavior, and the 366-day series limit.

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?

The description is tightly structured and front-loaded: it states what is returned, then covers the no-argument, date, and series modes. There is no filler, and every sentence contributes to correct invocation.

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?

Given four optional parameters, full schema coverage, and an output schema, the description provides enough detail to call the tool correctly across all modes. Its main gap is that it does not route the agent between this tool and dof_daily_summary.

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 parameter-level descriptions already carry much of the burden. The tool description adds value by explaining how parameters combine into modes and by clarifying that 'indicator' with 'from'/'to' produces a daily series limited to at most 366 days.

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 states a clear verb and resource (returns DOF-published financial indicators) and names the specific indicators: FIX, UDI, and TIIE. It does not explicitly differentiate this tool from the sibling dof_daily_summary, so it falls short of the top score.

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 clearly explains the three invocation modes: no arguments for today, date for that day, and indicator+from+to for a daily series. It also gives a useful preference hint to use a series for finding the most recent value, though it does not name sibling alternatives or exclusions.

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

Deploy Server

Other Tools