verificar_dataVerifica se uma data específica é feriado no Brasil. Use quando o usuário perguntar algo como "amanhã é feriado?", "25 de dezembro é feriado?", ou "segunda-feira vai ser feriado?". Retorna todos os feriados que caem naquela data (pode ter mais de um: nacional + municipal, por exemplo). Se retornar lista vazia, a data NÃO é feriado.
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Data no formato YYYY-MM-DD (ex: 2026-12-25) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully explains that the tool returns all holidays on the specified date, may return multiple entries (e.g., national + municipal), and that an empty list means the date is not a holiday. This goes beyond the schema.
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?
The description is concise and well-structured, consisting of three sentences that are front-loaded with the tool's purpose. Every sentence adds value without redundancy.
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 one-parameter tool with no output schema, the description covers core behavior, return semantics, and gives usage examples. It could mention error handling for invalid dates, but it is otherwise sufficiently complete for an AI agent to use correctly.
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?
The schema already fully documents the 'data' parameter with format and example (100% coverage). The description adds no additional parameter-specific meaning, so the baseline score of 3 applies.
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?
The description uses a specific verb 'Verifica' and identifies the resource as holidays in Brazil. It clearly states the tool checks a specific date and distinguishes itself from sibling tools that list holidays by category or region.
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 provides clear usage context with example user queries, such as 'amanhã é feriado?' and '25 de dezembro é feriado?'. It doesn't explicitly contrast with alternative tools or state when not to use, but the context strongly implies it's for single-date verification.
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.
Each tool has a clearly distinct purpose with no ambiguity. For example, 'buscar_feriados' is for general searches with multiple filters, while 'feriados_nacionais' and 'feriados_por_estado' target specific scopes, and 'verificar_data' checks a single date. The descriptions explicitly guide when to use each tool, preventing misselection.
Tool names follow a consistent verb_noun pattern in Portuguese, such as 'buscar_feriados', 'listar_estados', and 'verificar_data'. All names use snake_case and descriptive verbs like 'buscar', 'listar', and 'verificar', making the set predictable and readable.
With 9 tools, the count is well-scoped for the domain of Brazilian holidays. Each tool serves a specific function, from general searches to specialized checks and utility functions like listing states or municipalities, ensuring no tool feels redundant or missing for the server's purpose.
The tool set provides complete coverage for querying Brazilian holidays, including general searches, filters by type, location, and date, as well as utility tools for municipalities and states. It supports full workflows, such as finding IBGE codes before checking city holidays, and includes specialized checks for banking days, leaving no obvious gaps.