Skip to main content
Glama

Indicadores Argentina

Series disponibles

series_disponibles
Read-only

Catálogo de las series económicas argentinas que se pueden consultar (dólar, inflación, UVA, ICL, CER, riesgo país, tasas, comercio exterior por país y producto, recaudación por impuesto, balance cambiario, actividad por sector, consumo y confianza), con unidad, frecuencia y la fecha del primer y último dato. Gratis.

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": "series_disponibles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by saying the catalog includes unit, frequency, and first/last data dates, and that access is free, though it does not describe the response format or size.

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?

The description is a single front-loaded sentence that identifies the resource first. The parenthetical list of economic categories is long but helps convey coverage without unrelated filler.

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?

For a zero-parameter, read-only catalog tool with no output schema, the description gives enough detail about what the catalog contains and what fields each series carries. A minor gap is that it does not explicitly connect the returned catalog entries to the sibling serie_economica tool for fetching data.

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?

The tool takes zero parameters, so there is no parameter semantics burden on the description. Schema coverage is 100% and the empty object schema is consistent with a no-argument catalog call.

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 clearly states this is a catalog of Argentine economic series, enumerating concrete categories such as dólar, inflación, UVA, and riesgo país. It distinguishes itself from a data-retrieval tool like serie_economica by framing itself as a catalog of what can be consulted, though it does not explicitly name the sibling tool.

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?

The phrase 'que se pueden consultar' implies this tool is used to discover available series before querying one. However, it does not explicitly state when to use this versus serie_economica, nor does it provide exclusions or next-step guidance.

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