list_countriesList the ~30 European countries OpenHolidays covers, with their ISO codes and official languages. EUROPE-focused. Keyless.
| Name | Required | Description | Default |
|---|---|---|---|
| language | No | Language for country names, ISO 639-1 (default "EN"). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {}
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. Description adds value by stating 'Keyless' (no authentication needed) and specifying the coverage of ~30 European countries, which are behavioral traits beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. Front-loaded with the action and purpose, making it easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool with one optional parameter and no output schema, the description adequately covers purpose, scope, and keyless access. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter 'language' is described in the schema. Description does not add additional meaning to the parameter, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it lists ~30 European countries with ISO codes and official languages. The verb 'list' and resource 'countries' are specific, and it distinguishes from siblings like list_subdivisions by specifying European scope and OpenHolidays context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description notes 'EUROPE-focused', implying it should not be used for non-European countries. While it lacks explicit alternatives or when-not-to-use guidance, the scope is clear for a simple listing tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded; multiple Polymarket tools) and many serve unrelated domains, making it hard for an agent to distinguish which tool to use for a given task, especially given the server's holiday theme.
Most tool names follow a lowercase_with_underscores pattern, but the prefixes vary (ask_pipeworx, pipeworx_*, polymarket_*, etc.) and some names are less descriptive (e.g., process, run, execute-like vague verbs are absent, but still the naming lacks a unified convention across the broad set.
35 tools is excessive for a server named 'Openholidays'. The vast majority of tools (e.g., SEC filings, Polymarket, npm scanning) are unrelated to holidays, making the tool count feel bloated and unfocused.
For the holiday domain, the server includes necessary tools (list_countries, list_subdivisions, public_holidays, school_holidays) and is complete. However, the server's actual scope is far broader, and many unrelated tools are present, which dilutes the completeness for its stated purpose.