Skip to main content
Glama

Feriados nacionais

feriados_nacionais
Read-onlyIdempotent

Lists Brazilian national holidays for a given year with weekdays, including Carnival, Good Friday, and Corpus Christi, and can filter to upcoming dates.

Instructions

Lista os feriados nacionais de um ano (inclui Carnaval, Sexta-feira Santa e Corpus Christi), com o dia da semana de cada um.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "feriados_nacionais"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoNoAno, ex.: 2026 (padrão: ano atual)
apenas_proximosNoSó os feriados a partir de hoje (padrão: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description usefully discloses that movable holidays are included and that each entry carries the weekday, which is real behavioral context; it does not describe the date format or ordering of results, so it adds value without being rich.

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?

A single sentence that front-loads the action and resource, then appends the two scope details that matter (movable holidays, weekday). No filler or hedging; every clause earns its place.

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

Completeness4/5

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

For a simple two-optional-parameter read tool with full schema coverage and read-only/idempotent annotations, the description covers what is returned and notes the weekday field. The only gap is the exact output shape and date format, minor since no output schema exists but the tool is trivial.

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 description coverage is 100% – both 'ano' (example 2026, default current year) and 'apenas_proximos' (default false) are fully documented in the schema. The description mentions neither parameter, so it adds no meaning beyond the schema; baseline 3 applies.

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 ('Lista os feriados nacionais de um ano') and adds scope detail: movable holidays included (Carnaval, Sexta-feira Santa, Corpus Christi) and weekday per entry. An agent knows exactly what it gets, though there is no explicit differentiation from the closest sibling, calcular_dias_uteis.

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 description itself — 'de um ano' plus the schema's 'apenas_proximos' parameter suggest listing a year's holidays or upcoming ones. There is no explicit statement of when to prefer this over calcular_dias_uteis (business-day calculations), leaving the agent to infer the boundary.

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