Skip to main content
Glama

cattle-market

by ar.com.consignatarias

Calcular arrendamiento rural

calcular_arrendamiento
Read-onlyIdempotent

Calcula el canon de arrendamiento de campo (ARS) = kg novillo/ha/mes × hectáreas × precio. Devuelve canon mensual, anual y por ha/mes. Sin precio_novillo usa el índice oficial de arrendamientos del MAG (haciinfo000013), o el INMAG del día si falta. Solo calcula: para consultar precios usá get_indice_novillo o get_precios_hacienda. Estimación, no asesoramiento.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kg_haYesKg de novillo por hectárea. Por MES salvo que se pase periodo="anio" (típico 3-6 por mes, o 36-72 por año). Los avisos suelen publicarlo por año.
periodoNoUnidad de kg_ha. Por defecto "mes".
hectareasYesCantidad de hectáreas
precio_novilloNoPrecio del novillo ARS/kg (default: INMAG actual)

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds extra behavioral context: fallback to MAG official index or INMAG when precio_novillo is absent, and the 'Estimación, no asesoramiento' disclaimer. No contradiction with annotations.

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?

Concise, four-sentence description with formula front-loaded. Every sentence contributes meaning; no redundant or filler content.

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?

Explains return values (mensual, anual, per ha/mes) and fallback behavior, which is crucial since there is no output schema. Slightly incomplete in not addressing potential edge cases, but sufficient for a calculation tool.

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 covers 100% of parameters with detailed descriptions. The tool description adds the formula relating kg_ha, hectareas, and precio_novillo, but this is a minor addition beyond what the schema already provides.

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+resource: 'Calcula el canon de arrendamiento de campo' with a clear formula. Distinguishes from price lookup tools by explicitly saying 'Solo calcula' and referencing get_indice_novillo/get_precios_hacienda.

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?

Provides explicit guidance for when to use alternative price lookup tools ('para consultar precios usá get_indice_novillo o get_precios_hacienda'). However, it does not mention the sibling 'valuar_arrendamiento_campo', leaving potential ambiguity about when to choose this tool over that one.

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