Consignatarias · Argentine Cattle Market

Contexto macro ganadero

macro_context

Read-onlyIdempotent

Contexto macro del mercado ganadero argentino, sin parámetros: dólar blue y oficial (ARS), maíz FOB (USD/tn y ARS/kg), novillo INMAG (ARS/kg) y el spread novillo/maíz (kg de maíz que compra 1 kg novillo; proxy de rentabilidad de feedlot); y, si hay, índice de arrendamiento MAG (ARS/kg). NO da la serie INMAG (→cattle_price_index) ni precios por categoría (→livestock_prices). [EN] Argentine macro context for cattle trading: parallel and official USD rates, FOB corn, and the steer/corn spread.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`fuente`	Yes	Cita: página de consignatarias.com.ar que respalda el dato (utm_source=mcp) y fecha de consulta ISO (hora argentina).
`usd_blue`	Yes
`maiz_ars_kg`	Yes
`maiz_usd_tn`	Yes
`usd_oficial`	Yes
`novillo_ars_kg`	Yes
`kg_maiz_por_kg_novillo`	Yes
`indice_arrendamiento_oficial`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "fuente": {
+      "description": "Cita: página de consignatarias.com.ar que respalda el dato (utm_source=mcp) y fecha de consulta ISO (hora argentina).",
+      "properties": {
+        "consultado": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "url",
+        "consultado"
+      ],
+      "type": "object"
+    },
+    "indice_arrendamiento_oficial": {
+      "properties": {
+        "date": {
+          "type": "string"
+        },
+        "index": {
+          "type": "number"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "kg_maiz_por_kg_novillo": {
+      "type": "number"
+    },
+    "maiz_ars_kg": {
+      "type": "number"
+    },
+    "maiz_usd_tn": {
+      "type": "number"
+    },
+    "novillo_ars_kg": {
+      "type": "number"
+    },
+    "usd_blue": {
+      "type": "number"
+    },
+    "usd_oficial": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "usd_blue",
+    "usd_oficial",
+    "maiz_usd_tn",
+    "maiz_ars_kg",
+    "novillo_ars_kg",
+    "kg_maiz_por_kg_novillo",
+    "indice_arrendamiento_oficial",
+    "fuente"
+  ],
+  "type": "object"
+}

AddedOct 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine context beyond them: the zero-argument nature of the call and the conditional availability of the MAG lease index ("si hay"), which warns the agent a field may be absent. Return shape is covered by the output schema.

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?

Front-loaded with the resource and scoping, and every clause contributes content or routing. The main body is a single long sentence stacked with parentheticals and unit annotations, which is dense but still parseable; a bulleted or slightly split structure would read faster.

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?

An output schema exists, so return values need not be explained, yet the description still enumerates the key metrics and their units, which is exactly the right amount of detail. The sibling disambiguation and the optional-field caveat close the remaining gaps for a zero-parameter read tool.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description reinforces this with "sin parámetros", preventing an agent from inventing inputs.

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?

Names the exact resource (macro context for the Argentine cattle market) and enumerates its contents: blue/official USD rates, FOB corn, steer INMAG, the steer/corn spread and an optional MAG lease index. It explicitly disclaims two neighboring capabilities and routes them to cattle_price_index and livestock_prices, so an agent can distinguish it from siblings 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?

States "sin parámetros" up front, which tells the agent this is a zero-input call, and gives explicit exclusions with named alternatives ("NO da la serie INMAG (→cattle_price_index) ni precios por categoría (→livestock_prices)"). Both when-it-applies and when-to-go-elsewhere are covered.

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 tools Inspect

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.