Consignatarias · Argentine Cattle Market

Valuar una tropa de hacienda

value_cattle_lot

Read-onlyIdempotent

¿Cuánto valen 350 novillos en Formosa? Valúa una tropa de hacienda con la BANDA de precio realmente observada en las operaciones de lote del MAG (VR v1.0): conservador (P10), central (mediana) y optimista (P90), con la cantidad de lotes y cabezas que la sostiene, más el total en USD (blue y oficial) y la fuente fechada. Cuando una categoría no tiene base suficiente de lotes cae a la referencia nacional del MAG y lo declara — nunca inventa un rango. Metodología: https://www.consignatarias.com.ar/metodologia/vr. GRATIS y sin cupo. Params: categoria, cabezas, kg_promedio (opcional, si no se asume el peso típico de venta), provincia (opcional). [EN] Value a lot of cattle in Argentina: returns the observed P10/median/P90 price band, not a single point.

Input Schema

Name	Required	Description
`cabezas`	Yes	Cantidad de animales (1 a 100.000)
`categoria`	Yes	Categoría MAG
`provincia`	No	Provincia (opcional; la referencia de precio es nacional MAG)
`kg_promedio`	No	Peso vivo promedio en kg (opcional; default: peso típico de venta de la categoría)

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).
`origen`	No	De dónde salen los precios (MAG + dolarapi.com).
`cabezas`	Yes
`usd_blue`	No
`categoria`	Yes
`provincia`	No
`total_ars`	Yes
`valuacion`	Yes
`kg_asumido`	No
`referencia`	No	Referencia VR v1.0: banda observada, ventana y límites.
`kg_promedio`	Yes
`usd_oficial`	No
`fecha_indice`	No
`precio_kg_ars`	Yes
`precio_kg_mag`	Yes
`total_usd_blue`	Yes
`brecha_vs_mag_pct`	No
`total_usd_oficial`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "brecha_vs_mag_pct": {
+      "type": "number"
+    },
+    "cabezas": {
+      "type": "number"
+    },
+    "categoria": {
+      "type": "string"
+    },
+    "fecha_indice": {
+      "type": "string"
+    },
+    "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"
+    },
+    "kg_asumido": {
+      "type": "boolean"
+    },
+    "kg_promedio": {
+      "type": "number"
+    },
+    "origen": {
+      "description": "De dónde salen los precios (MAG + dolarapi.com).",
+      "type": "string"
+    },
+    "precio_kg_ars": {
+      "type": "number"
+    },
+    "precio_kg_mag": {
+      "type": "number"
+    },
+    "provincia": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "referencia": {
+      "description": "Referencia VR v1.0: banda observada, ventana y límites.",
+      "type": "object"
+    },
+    "total_ars": {
+      "type": "number"
+    },
+    "total_usd_blue": {
+      "type": "number"
+    },
+    "total_usd_oficial": {
+      "type": "number"
+    },
+    "usd_blue": {
+      "type": "number"
+    },
+    "usd_oficial": {
+      "type": "number"
+    },
+    "valuacion": {
+      "properties": {
+        "central_ars": {
+          "type": "number"
+        },
+        "conservador_ars": {
+          "type": "number"
+        },
+        "optimista_ars": {
+          "type": "number"
+        },
+        "uso_banda": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "conservador_ars",
+        "central_ars",
+        "optimista_ars",
+        "uso_banda"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "categoria",
+    "cabezas",
+    "kg_promedio",
+    "precio_kg_ars",
+    "precio_kg_mag",
+    "total_ars",
+    "total_usd_blue",
+    "total_usd_oficial",
+    "valuacion",
+    "fuente"
+  ],
+  "type": "object"
+}

AddedOct 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations (readOnly/openWorld/idempotent, non-destructive), it discloses meaningful behavior: never invents a range, degrades to national reference and says so, reports the sample size behind the band, includes both blue and official USD rates, and is free with no quota. That is substantive, though the return details partially overlap with the existing 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?

The hook question is front-loaded and earns its place by demonstrating the input shape, and the fallback/methodology notes are relevant. Some waste remains: the trailing parameter list duplicates the schema and the [EN] sentence repeats already-covered meaning.

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 read-only valuation tool with four params, full schema coverage and an output schema, the description covers what an agent needs: what it returns, what happens when data is thin, and how to call it. Nothing material is missing.

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% with an enum on categoria, so the schema already carries the parameter burden. The description only restates the params and the kg_promedio default, adding little beyond what the schema and its descriptions already say.

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 (valúa una tropa de hacienda) plus the exact output shape: P10/median/P90 band from observed MAG lot operations, with lot/head backing, USD totals and dated source. The quantity-based scoping ('¿Cuánto valen 350 novillos?') makes it clearly distinct from index-style siblings like livestock_prices, cattle_price_index or price_dispersion_history.

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

Usage Guidelines4/5

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

The leading example establishes the use case concretely, and the description gives an explicit fallback rule (falls back to MAG national reference and declares it when a category lacks lot depth) plus notes which params are optional and what happens when kg_promedio is omitted. It does not name a competing sibling to route away from, so it stops short of a 5.

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.