Skip to main content
Glama

El Tablero: Argentina economic data

Search Argentine economic series

search_series
Read-onlyIdempotent

Find Argentine economic time series by keywords and get their keys. Call this first whenever you don't already know a series key, then pass the key to get_series (history) or get_projection (forecast). Covers BCRA (exchange rates, reserves, interest rates, monetary aggregates, UVA, CER), INDEC via datos.gob.ar (inflation, activity, wages, trade, employment, poverty) and derived series (real rate, FX gap). Matches every word, ignoring accents and case; series names are in Spanish, so Spanish keywords work best ("inflacion", "dolar", "reservas", "badlar", "salarios"). Returns up to 15 matches with key, name, category, source and page URL; an empty list means no match, not an error. Read-only, no side effects, no authentication. Rate limited to 60 calls per minute per IP. Data updates at most once per business day.

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": {
      "query": "<query>"
    },
    "name": "search_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords to match against series names and categories, e.g. "inflacion mensual" or "tipo de cambio".

Output Schema

NameRequiredDescriptionDefault
noteNo
queryYes
resultsYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile, but the description adds material context they do not: a 60 calls/minute per IP rate limit, once-per-business-day data freshness, matching semantics (every word, accent- and case-insensitive), and a 15-result cap. These are exactly the operational traits that affect how an agent plans calls.

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?

Front-loads the action and the call-first rule, then layers sourcing coverage, matching behavior, and operational limits in descending priority. Dense but every sentence carries actionable information; no filler.

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 single-parameter search tool with full schema coverage, annotations, and an output schema, this covers everything an agent needs: when to call, what it returns at a high level, and the operational constraints. Return-field details are rightly left to the output schema.

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 real meaning beyond the schema: the keyword language (Spanish names, with concrete examples like "inflacion", "dolar", "badlar") and the all-words-must-match rule. Minor remaining gap: nothing about how to broaden a query that returns no matches.

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 ("Find Argentine economic time series by keywords and get their keys") and immediately differentiates itself from the key-consuming siblings get_series and get_projection. An agent can identify the tool's role without opening the schema.

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?

Gives an explicit ordering rule ("Call this first whenever you don't already know a series key") and names the downstream alternatives for history vs. forecast. It also sets expectations for the no-match case, so the agent knows not to retry or treat an empty list as failure.

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