MCP Europe Tools

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

get_portugal_holidays

Read-onlyIdempotent

Returns all Portuguese national public holidays for a given year as a structured list. Each holiday includes { date: 'YYYY-MM-DD', name: string, name_en: string }. Returns 10 mandatory national holidays defined by Portuguese law. Use when calculating business deadlines, delivery dates, payment due dates, SLA periods, or scheduling tasks that must avoid non-working days in Portugal. Does not include municipal or regional holidays (e.g. Lisbon June 13, Porto June 24) which vary by city.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes	Calendar year as a 4-digit integer. Example: 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations provide readOnlyHint and idempotentHint, and the description adds meaningful behavioral details: the exact output structure, the count (10 mandatory national holidays defined by law), and the exclusion of municipal/regional holidays. This goes beyond the annotation-only safety profile.

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?

Three sentences, front-loaded with purpose, then output structure, use cases, and exclusions. No unnecessary words; every sentence adds value.

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 simple tool with one parameter and no output schema, the description covers function, output format, scope, and limitations. An agent has enough context to decide when to use it and interpret results.

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?

The input schema fully documents the 'year' parameter with type and example, so description doesn't need to add more. The phrase 'for a given year' reinforces but doesn't extend schema information. Baseline 3 is appropriate given high schema coverage.

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 clearly states the tool 'Returns all Portuguese national public holidays for a given year as a structured list,' with specific verb and resource. It distinguishes from sibling country-holiday tools by explicitly naming Portugal and excluding 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?

Explicit usage context is provided: 'Use when calculating business deadlines, delivery dates, payment due dates, SLA periods, or scheduling tasks that must avoid non-working days in Portugal.' It also gives a clear exclusion ('Does not include municipal or regional holidays'), guiding agents away from inappropriate use.

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

All MCP Europe 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.4/5.0

Disambiguation5/5

Each tool targets a distinct resource and action. Multiple validators are differentiated by country and entity type (NIF, SIRET, TVA, IBAN). The only potential overlap is between calculate_working_days and get_portugal_holidays, but their purposes are clearly distinct: one counts days, the other lists holidays.

Naming Consistency3/5

Most tools follow a lowercase verb_noun pattern, but country encoding is inconsistent: some use prefix (get_france_holidays), some suffix (validate_nif_es), and some omit it entirely (validate_nif, validate_siret). The verb set is consistent (get, validate, calculate, format), but the inconsistencies in noun structure prevent a perfect score.

Tool Count5/5

11 tools is well within the ideal range for a domain-specific server. Each tool covers a distinct utility and the count is appropriate for the stated European business scope.

Completeness3/5

The server provides holiday data for France, Spain, and Portugal, but only calculates working days for Portugal. There is no working-days calculation for France or Spain despite equivalent holiday tools existing. Additionally, tax ID validation is limited to Portugal, Spain, and France, leaving other supported VAT/IBAN countries without fiscal identifier validation. These are notable gaps that affect agents handling non-Portuguese deadlines.

Resources

Need Help?