MCP LatAm Tools

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

get_brazil_holidays

Read-onlyIdempotent

Returns Brazilian national public holidays for any given year. Use this tool when calculating delivery dates, scheduling appointments, computing working days, or any task requiring knowledge of non-working days in Brazil. Returns all national holidays with dates in YYYY-MM-DD format and names in both Portuguese and English. Note: Brazil also has state and municipal holidays which vary by location and are not included here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes	The year to get holidays for. Example: 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by disclosing the return format (YYYY-MM-DD), bilingual names (Portuguese and English), and the exclusion of state/municipal holidays, which goes beyond the annotations and provides useful behavioral context.

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, front-loaded with the core purpose, followed by usage scenarios and return details. Every sentence contributes meaningful information without redundancy.

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?

No output schema exists, but the description clearly explains what is returned (dates in YYYY-MM-DD and names in Portuguese/English) and notes limitations (state/municipal holidays excluded). This makes it complete for the tool's simple scope.

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 coverage is 100% for the single 'year' parameter with description and example provided. The description does not add much beyond mentioning 'any given year', so baseline 3 is appropriate; no need for further compensation.

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 starts with 'Returns Brazilian national public holidays for any given year', which is a specific verb+resource combination. It clearly distinguishes from sibling tools for other countries by specifying 'Brazilian' and further clarifying it covers only national, not state or municipal, holidays.

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: 'Use this tool when calculating delivery dates, scheduling appointments, computing working days, or any task requiring knowledge of non-working days in Brazil.' It also notes state and municipal holidays are not included, which guides against alternative tools that might cover those.

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 tools Inspect

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

Need Help?