Skip to main content
Glama

cattle-market

by ar.com.consignatarias

Buscar frigorífico

buscar_frigorifico
Read-onlyIdempotent

Directorio de frigoríficos y plantas de faena habilitados MAGYP/SENASA (1.102). Buscá por nombre, CUIT o provincia. Por planta devuelve nombre, provincia, matrícula, CUIT y ciclo; marca las inactivas en SENASA. Requiere query (nombre/CUIT) o provincia (una alcanza); limite default 10, máx 30. No da precios ni faena — es directorio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoNombre o CUIT a buscar (opcional si se pasa provincia)
limiteNoMáximo de resultados (default 10)
provinciaNoFiltra por provincia

TDQS

A4.4/5.0
Behavior4/5

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

Las anotaciones ya declaran readOnlyHint=true y destructiveHint=false. La descripción añade valor al especificar que marca las plantas inactivas en SENASA y describe los campos devueltos (nombre, provincia, matrícula, CUIT, ciclo). No contradice las anotaciones.

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?

La descripción es un párrafo bien estructurado que incluye todos los elementos clave: propósito, parámetros, comportamiento y limitaciones. Cada oración aporta información útil, sin repeticiones innecesarias.

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?

La descripción es completa para la complejidad de la herramienta: cubre el origen de datos (1.102 registros), criterios de búsqueda, estructura de respuesta (nombre, provincia, matrícula, CUIT, ciclo, inactivas), restricciones (query o provincia) y límites. Al no haber esquema de salida, la descripción compensa adecuadamente.

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?

La cobertura del esquema es del 100%, pero la descripción añade información: requiere al menos 'query' o 'provincia' (aclara opcionalidad relativa), y para 'limite' especifica máximo 30 (el esquema solo menciona default 10). Esto supera la línea base de 3.

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?

La descripción especifica claramente el verbo 'Buscar' y el recurso 'frigoríficos y plantas de faena habilitados', distinguiéndose de herramientas hermanas como 'buscar_consignataria' que se enfocan en consignatarias. Indica explícitamente que no da precios ni faena, diferenciándose de otras herramientas de precios.

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?

La descripción indica cuándo usar la herramienta (para buscar frigoríficos por nombre, CUIT o provincia) y qué no hace (no da precios ni faena). Aunque no menciona explícitamente alternativas, el contexto de las herramientas hermanas y la frase 'es directorio' guían adecuadamente al agente.

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

All cattle-market toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a specific, well-defined aspect of the cattle market domain. Overlaps are minimal and clearly disambiguated in descriptions (e.g., get_precios_hacienda vs. get_precios_detallados vs. get_indice_novillo). Even similar-sounding tools like calcular_arrendamiento and valuar_arrendamiento_campo have distinct purposes (simple calculation vs. valuation with currency options).

Naming Consistency3/5

Tool names mix Spanish and English verb patterns (e.g., 'get_indice_novillo' vs. 'buscar_consignataria', 'contratar_pro_consignataria' vs. 'list_remates'). While each subgroup (sanidad_*, get_*) maintains internal consistency, the overall naming is not unified. However, names are still descriptive and readable.

Tool Count5/5

With 22 tools, the server covers a broad domain (prices, health, directories, valuations, alerts) without feeling bloated. Each tool earns its place, providing meaningful functionality. The count is well-scoped for the Argentine cattle market context.

Completeness5/5

The tool surface covers the full lifecycle: market data (prices, indices, historical), consignment and slaughterhouse directories, health regulations and movement requirements, valuation tools, alerts, and even a buyer matching service. There are no obvious gaps for the stated purpose of a cattle market MCP server.

Resources