Skip to main content
Glama

Get Indicators

get_indicators
Read-onlyIdempotent

Retrieve Mexico's DOF-published FIX exchange rate, UDIS, and TIIE indicators for a given date, returning the preceding publication when no data appears that day.

Instructions

Get the financial indicators published in the DOF: FIX exchange rate, UDIS and TIIE.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDOF publication date. If nothing was published that day (weekend, holiday) the latest earlier publication is returned.today

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so safety and repeatability are covered without the description. The description's added behavioral content is limited to naming the three indicator families; it says nothing about response shape, units, or what happens when no data exists beyond what the schema already states.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the enumerated indicator list slightly crowds out information that would have been more useful, such as routing versus the history tool.

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?

For a simple read-only single-parameter tool with an output schema and full annotations, the essentials of safety, parameters, and return values are already covered by structured fields. The remaining gap is disambiguation from get_indicator_history, which the description does not address.

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?

Only one parameter exists and schema description coverage is 100%, including the weekend/holiday fallback to the latest earlier publication. The description adds no date format, timezone, or range guidance, so it neither compensates for nor improves on the schema; baseline 3 applies.

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') and resource ('financial indicators published in the DOF') and enumerates the actual values returned (FIX, UDIS, TIIE), so the agent knows exactly what data comes back. It does not, however, distinguish itself from the sibling get_indicator_history, which reads as an overlapping resource.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no mention of the closest alternative (get_indicator_history) or when that would be preferable. The only implication of usage comes from the word 'published' and the date parameter's default of 'today', the rest 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.