Skip to main content
Glama

list_national_holidays

Retrieve Brazilian national holidays for a specified year (1900–2199) to support scheduling, compliance planning, and date calculations in applications.

Instructions

List Brazilian national holidays for a year.

Args: year: Year between 1900 and 2199.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>"
    },
    "name": "list_national_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose a real constraint the schema lacks — the valid year range 1900–2199 — and 'List' implies a read-only operation with no side effects. However it says nothing about the return shape (date format, holiday names) and no output schema exists to compensate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two lines, front-loaded with the purpose before the argument detail; nothing is padded. The Google-style 'Args:' block is slightly heavier than needed for one parameter but still earns its place by carrying the year range.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A single-parameter tool is simple, and the description covers the input adequately. The gap is the untold output: with no output schema, an agent cannot know whether the response contains dates only, names, or a type classification — a notable omission for a 'list' tool.

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 coverage is 0% (the schema declares only 'integer' titled 'Year'), so the description must supply meaning, and it does: it gives the accepted domain 1900–2199, which prevents invalid calls. It stops short of stating format expectations or behavior for out-of-range years, so it is not a full compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List Brazilian national holidays') plus scope ('for a year'), which is enough to separate it from the sibling lookups (CEP, bank, IPCA, PTAX, SELIC). It does not explicitly name or contrast a sibling, but none of the visible siblings is a plausible substitute, so the differentiation is adequate rather than exemplary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the purpose: an agent knows to call this when it needs holiday dates for a year. There is no explicit when-to-use/when-not-to-use statement, no note on jurisdiction limits beyond 'Brazilian national' (e.g. no state/municipal holidays), and no prerequisites.

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