Skip to main content
Glama

cattle-market

by ar.com.consignatarias

Buscar consignataria

buscar_consignataria
Read-onlyIdempotent

Directorio de consignatarias/casas de remate de hacienda por nombre, razón social o localidad (query, mín 2 car). Devuelve nombre, localidad/provincia, categoría, CUIT, un contacto (WhatsApp/teléfono/web) y el perfil en consignatarias.com.ar. Opcional: provincia; limite (def 8, máx 25). NO da actividad de mercado: para cabezas/precio en el MAG usá actividad_consignatarias.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNombre, localidad o razón social a buscar
limiteNoMáximo de resultados (default 8)
provinciaNoFiltra por provincia (opcional)

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds useful behavioral context: default and max for results, clarification that it does not provide market activity, and specifics about returned fields. No contradictions.

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

Conciseness5/5

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

The description is concise with no fluff. It front-loads the main purpose, provides essential usage details, and ends with a clear exclusion. Every sentence adds value.

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?

Despite no output schema, the description thoroughly describes what is returned (nombre, localidad/provincia, categoría, CUIT, contacto, perfil). With 3 well-explained parameters and clear behavior, the tool is fully specified for correct invocation.

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%, but the description adds constraints not in schema: minimum query length (2 chars), default for limite (8), maximum (25). Also clarifies that provincia is optional.

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?

The description uses a specific verb ('Buscar' meaning search) and resource ('Directorio de consignatarias/casas de remate'). It clearly distinguishes from sibling 'actividad_consignatarias' by stating what it does not do (market activity).

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 when to use (search directory) and when not (for market activity, use actividad_consignatarias). Also includes minimum query length (2 chars) and default/max for limite.

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