Skip to main content
Glama

Consignatarias · Argentine Cattle Market

by ar.com.consignatarias
OverviewDiscussionsAdmin

Histórico del Índice Novillo (INMAG)

inmag_history
Read-onlyIdempotent

Serie histórica del Índice Novillo (INMAG) — TENDENCIA. Serie diaria desde 2015-01-05: MAG/Cañuelas desde may-2022, antes era Mercado de Liniers (índice empalmado; la respuesta lo aclara cuando el rango cruza esa frontera). Devuelve valor inicial y final, variación %, mínimo, máximo, nº de ruedas y una muestra (~8 puntos). Índice DIARIO ponderado por volumen. Rango: dias (ventana atrás, default 30) o desde/hasta (YYYY-MM-DD, exacto — sirve para una fecha puntual: desde=hasta, GRATIS a cualquier profundidad). moneda: ars (default) o usd (dólar blue venta, último valor conocido a cada fecha). GRATIS y sin cupo a CUALQUIER profundidad, desde 2015-01-05: la consulta no tiene techo. Devuelve el análisis completo (inicio, fin, variación, mínimo, máximo) con una muestra de ~8 puntos. Si lo que necesitás es la serie fila por fila para cargarla en tu propio modelo, eso va por API key Enterprise o US$0,25 en USDC vía x402 (/api/x402/inmag-historico) — se cobra la descarga masiva y la redistribución, no la consulta. Valor de HOY → cattle_price_index; por categoría (semanal) → livestock_prices, no comparar 1:1. [EN] Historical Argentine cattle price series (INMAG) since 2015, in ARS or USD. Free, no cap, any window.

Input Schema

NameRequiredDescriptionDefault
diasNoVentana en días hacia atrás (default 30, máx 5000; la serie arranca 2015-01-05). Sin techo: cualquier ventana responde gratis. Ignorado si se pasa desde/hasta.
desdeNoFecha inicial YYYY-MM-DD (opcional; la serie arranca 2015-01-05)
hastaNoFecha final YYYY-MM-DD (opcional; default hoy). desde=hasta consulta una fecha puntual.
monedaNoars (default) o usd — conversión por dólar blue venta, último valor conocido a cada fecha (regla de /mercado/inmag-dolares)
api_keyNoAPI key Enterprise (cnsg_live_...). Opcional y ya no necesaria para la consulta: sirve para la descarga masiva fila por fila y los exports. Si ya va por el header Authorization: Bearer, no hace falta acá.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds substantial context beyond them: no rate cap at any depth, the data-lineage caveat that pre-May-2022 values come from Mercado de Liniers and the response flags range crossings, the USD conversion rule (blue venta, last known value per date), and what is actually monetized (mass download/redistribution, not the query).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and information-packed, but redundant: the return payload (inicio/fin/variación/min/máx/~8 points) and the free/no-cap claim are each stated two or three times, and the [EN] one-liner duplicates the opening sentence. Editing out the repetition would tighten it without losing content.

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?

No output schema exists, so the description rightly describes the returned fields and sample size, and it covers cost, depth and the provenance boundary an agent needs to interpret results. Only minor gaps remain (e.g. exact behavior on out-of-range dates), but the essential picture is complete.

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?

Schema description coverage is 100% and the schema already documents dias (default 30, max 5000), desde/hasta (default today, desde=hasta = single date) and moneda (blue venta rule). The description restates these but adds negligible new syntax or edge-case meaning beyond what the schema provides, so the baseline 3 applies.

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+resource ('Serie histórica del Índice Novillo (INMAG)'), its cadence and depth (daily since 2015-01-05, spline-spliced market switch in May-2022), and explicitly disambiguates from siblings: today's value goes to cattle_price_index, weekly by-category to livestock_prices. An agent can route without opening any 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?

Explicit when-to-use-this vs alternatives ('Valor de HOY → cattle_price_index; por categoría (semanal) → livestock_prices, no comparar 1:1'), plus the row-by-row case routed to Enterprise API key or x402. Also clarifies fresh-vs-historical and warns against a naive 1:1 comparison.

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

All Consignatarias · Argentine Cattle Market toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources