Skip to main content
Glama

MCP Europe Tools

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

format_number_european

Read-onlyIdempotent

Formats a number using the locale conventions of a specific European country, applying the correct decimal separator and thousands separator. Returns { original: number, formatted: string, locale: string, country_code: string }. Different European countries use different conventions — Portugal and most of continental Europe use '1.234,56' (dot as thousands, comma as decimal), while Ireland uses '1,234.56'. Supports PT, ES, FR, DE, IT, NL, BE, PL, SE, DK, FI, AT, IE, GR, HU, RO. Use when displaying prices, measurements, or any numeric value to end users in a specific European country.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesThe numeric value to format. Example: 1234.56
decimalsNoNumber of decimal places. Defaults to 2. Use 0 for whole numbers, 2 for prices.
country_codeYesTwo-letter country code for the target locale. Example: 'PT', 'FR', 'DE'

TDQS

A4.5/5.0
Behavior4/5

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

Annotations establish read-only and idempotent behavior; description adds that it returns an object with original, formatted, locale, and country_code. It also discloses that different countries use different separators, giving concrete examples. This is valuable context beyond the 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 sentences with zero redundancy. Front-loads the action, includes a return type, examples, and supported countries. Everything earns its place.

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 formatting utility, the description covers purpose, usage, supported inputs, and output format. Since no output schema exists, the explicit return type is crucial and provided. No critical information is missing.

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 covers all three parameters with descriptions, so baseline is 3. The description adds the context of European decimal conventions and lists supported country codes, enriching the semantics of country_code. However, it doesn't add information about the 'number' or 'decimals' parameters beyond the schema, so a 4 is appropriate.

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 formats a number using European locale conventions, with a specific verb ('Formats') and resource. It distinguishes itself from sibling tools (holidays, VAT, validation) by being the only formatting tool, and further differentiates internal behavior by country. The description is unambiguous and specific.

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?

Explicitly states 'Use when displaying prices, measurements, or any numeric value to end users in a specific European country', providing clear context. It also lists supported country codes and examples of conventions. While it doesn't mention alternatives, the sibling tools are clearly unrelated, so the guidance is sufficient.

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