Skip to main content
Glama

cattle-market

by ar.com.consignatarias

contratar_pro_consignataria

contratar_pro_consignataria
Read-onlyIdempotent

Cotiza y explica cómo activar PRO Consignataria pagando en USDC (x402): perfil destacado, badge PRO, video del último remate y leads en consignatarias.com.ar. Mismo producto que en /planes (ARS 45.000/mes), cotizado al dólar blue del día. Esta tool NO cobra: devuelve el monto exacto y el endpoint x402 para pagar. Params: slug (consignataria del directorio, usá buscar_consignataria si no lo sabés), meses (1-12, default 1).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug de la consignataria en el directorio
mesesNoMeses a contratar (1-12, default 1)

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint false. Description confirms non-destructive behavior by stating 'NO cobra: devuelve el monto exacto y el endpoint x402 para pagar.' Adds context about currency conversion and product equivalence with /planes.

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?

Single paragraph with clear front-loading of main purpose. Each sentence contributes distinct information. Could be slightly more structured (e.g., separate lines for params) but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description clarifies output includes exact amount and x402 endpoint. Given low complexity (2 simple params), this is sufficient for an agent to understand and use the 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?

Schema covers 100% of parameters with brief descriptions. Description adds value by advising to use 'buscar_consignataria' if slug unknown and specifying valid range for 'meses' (1-12, default 1).

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?

Explicitly states it 'cotiza y explica cómo activar PRO Consignataria pagando en USDC (x402)' and lists included features. References sibling tool 'buscar_consignataria' for slug lookup, differentiating it from other tools.

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?

Instructs to use 'buscar_consignataria' if slug unknown and clarifies that the tool does not process payment. However, it does not explicitly state when to avoid this tool (e.g., if already subscribed or not interested in PRO plan).

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