Consignatarias · Argentine Cattle Market

Próximos remates de hacienda

upcoming_auctions

Read-onlyIdempotent

Calendario de próximos remates de hacienda en Argentina: solo programados, fecha ≥ hoy, ordenados por fecha. Devuelve fecha, hora, consignataria, localidad/provincia, categoría principal y si hay transmisión en vivo. Params: provincia (subcadena, opcional), limite (default 10, máx 50). No da precios ni INMAG: usá livestock_prices/cattle_price_index. [EN] Calendar of upcoming Argentine cattle auctions, filterable by province.

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

Input Schema

Name	Required	Description	Default
`limite`	No	Máximo de remates (default 10)
`provincia`	No	Filtra por provincia (ej. "Buenos Aires")

Output Schema

Name	Required	Description
`corte`	No	Presente solo si el listado se cortó por el techo de consultas.
`fuente`	Yes	Cita: página de consignatarias.com.ar que respalda el dato (utm_source=mcp) y fecha de consulta ISO (hora argentina).
`region`	No	Solo cuando la provincia pedida no tiene remates: los más cercanos, de su región.
`remates`	Yes
`sugerencia`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "corte": {
+      "description": "Presente solo si el listado se cortó por el techo de consultas.",
+      "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"
+    },
+    "region": {
+      "description": "Solo cuando la provincia pedida no tiene remates: los más cercanos, de su región.",
+      "properties": {
+        "codigo": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "nombre": {
+          "type": "string"
+        },
+        "remates": {
+          "items": {
+            "properties": {
+              "categoria": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "consignataria": {
+                "type": "string"
+              },
+              "consignataria_slug": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "date": {
+                "type": "string"
+              },
+              "en_vivo": {
+                "type": "boolean"
+              },
+              "lugar": {
+                "type": "string"
+              },
+              "provincia": {
+                "type": "string"
+              },
+              "time": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "date",
+              "time",
+              "consignataria",
+              "lugar",
+              "provincia",
+              "categoria",
+              "en_vivo"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "codigo",
+        "nombre",
+        "remates"
+      ],
+      "type": "object"
+    },
+    "remates": {
+      "items": {
+        "properties": {
+          "categoria": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "consignataria": {
+            "type": "string"
+          },
+          "consignataria_slug": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "date": {
+            "type": "string"
+          },
+          "en_vivo": {
+            "type": "boolean"
+          },
+          "lugar": {
+            "type": "string"
+          },
+          "provincia": {
+            "type": "string"
+          },
+          "time": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "date",
+          "time",
+          "consignataria",
+          "lugar",
+          "provincia",
+          "categoria",
+          "en_vivo"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sugerencia": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "remates",
+    "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 cover readOnly/idempotent/openWorld/non-destructive, so the safety profile is free. The description then adds genuine behavioral context beyond them: only future scheduled auctions, date-ascending ordering, default 10 with a hard cap of 50, and live-broadcast flag in the response.

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 purpose and scope, then return fields, then params, then exclusions — a sensible ordering with no filler. The trailing [EN] one-liner is mildly duplicative of the opening sentence but aids routing.

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?

Two-parameter, read-only tool with an output schema and full schema coverage. The description covers scope, ordering, defaults, caps, filter semantics, and the nearest alternatives — nothing an agent needs for correct invocation is missing.

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 baseline is 3, but the description adds meaning the schema lacks: provincia is a substring match (not exact) and is optional, and limite has a maximum of 50 that the schema description omits.

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 a specific resource and scope: a calendar of upcoming Argentine cattle auctions, restricted to future-dated scheduled events, ordered by date. It also enumerates the returned fields, so an agent knows exactly what it is getting 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?

Explicitly states the negative case and routes elsewhere: no prices or INMAG here, use livestock_prices/cattle_price_index. Combined with the 'solo programados, fecha ≥ hoy' constraint, an agent can decide between this and the price siblings without inference.

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.