Skip to main content
Glama

cattle-market

by ar.com.consignatarias

Validar / decodificar RENSPA

sanidad_renspa
Read-onlyIdempotent

Valida y decodifica un código RENSPA (Registro Nacional Sanitario de Productores Agropecuarios): 17 caracteres, formato 00.000.0.00000.00. Devuelve los segmentos (provincia, departamento, jurisdicción de oficina local, establecimiento y productor) y explica qué identifica. NO consulta la vigencia en vivo (la base de SENASA está tras clave fiscal ARCA); para verificar vigencia remite a la consulta pública oficial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
renspaYesCódigo RENSPA, con o sin puntos (ej. 01.234.5.67890.12)

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds critical context: it does NOT query live SENASA database due to authentication requirements, directing to official public query for validity. 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?

Two well-structured sentences: first states core function and output, second clarifies limitation and alternative. No wasted words.

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, description explains returned segments and their meaning. Covers limitation and alternative for full verification. Complete for a simple validation 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 description covers 100% with 'Código RENSPA, con o sin puntos'. Description adds format structure and what the decoded segments represent, providing additional clarity beyond schema.

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?

Clearly states it validates/decodes a RENSPA code, gives format (17 chars, 00.000.0.00000.00), and explains it returns segments (provincia, departamento, etc.). Distinguishes from sibling tools by specificity.

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 what it does (validate/decode) and what it does NOT do (live validity check). Provides alternative for verification: 'remite a la consulta pública oficial'.

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