Skip to main content
Glama

MCP LatAm Tools

by app.railway.up.mcp-latam-tools-production

validate_cuit

Read-onlyIdempotent

Validates an Argentine CUIT (Código Único de Identificación Tributaria) using the official AFIP checksum algorithm. CUIT is used by companies, self-employed workers, and other entities for tax purposes. Use this tool when processing Argentine invoices, supplier registrations, B2B transactions, or any document requiring a valid Argentine tax identifier. Accepts CUIT with or without formatting (dashes). Returns whether the CUIT is valid, the entity type detected, and the cleaned CUIT.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cuitYesThe Argentine CUIT to validate. Formatting (dashes) is automatically removed. Example: '30-12345678-9' or '30123456789'

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description discloses that the tool uses the official AFIP checksum algorithm, accepts both formatted and unformatted CUITs, automatically removes dashes, and returns validity, entity type, and cleaned CUIT. This gives the agent a full behavioral picture.

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 three sentences long, front-loaded with the purpose, then usage guidance, then behavior and return values. Every sentence earns its place with no redundancy or filler.

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?

For a single-parameter validation tool with readOnly and idempotent annotations, the description is complete: it covers purpose, usage triggers, input flexibility, algorithm, and output fields. No output schema exists, but the description explicitly states what is returned, filling that gap.

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?

The schema already covers 100% of the parameter with a description and example. The tool description adds value by clarifying that both formatted and unformatted CUITs are acceptable and that the tool returns a cleaned version, reinforcing parameter meaning beyond the 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?

The description opens with 'Validates an Argentine CUIT' using a specific verb and resource, clearly identifying what the tool does. It also distinguishes from sibling validation tools by specifying Argentina's CUIT and the official AFIP checksum algorithm.

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?

The description explicitly states when to use the tool: 'Use this tool when processing Argentine invoices, supplier registrations, B2B transactions, or any document requiring a valid Argentine tax identifier.' It provides clear context but does not mention exclusions or alternatives, so it stops short of a 5.

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

All MCP LatAm Tools 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.5/5.0
Disambiguation5/5

Each tool targets a distinct resource (a specific country's holidays or a specific identifier type). The four holiday tools are clearly separated by country, and the seven validation tools are each for a different document or identifier (CNPJ, CPF, CUIL, CUIT, PIX key, RFC, RUT). No two tools appear to overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent pattern: get_<country>_holidays for holiday lookups and validate_<identifier> for validation. Naming is entirely lowercase snake_case with a clear verb prefix, making it easy to predict tool names.

Tool Count5/5

With 11 tools, the server is well-scoped for its purpose of providing Latin American business utilities. The set is neither too sparse nor overly large, and each tool contributes a distinct function. This count is appropriate for the intended domain.

Completeness4/5

The tool surface covers the major Latin American economies (Argentina, Brazil, Chile, Mexico) for both holidays and key identifiers. Minor gaps exist, such as missing validation for Peruvian RUC or Colombian NIT, and holiday coverage is limited to four countries. However, the core workflows for the included countries are well covered.

Resources