brasil-mcp-essentials

Official

by brasil-mcp

Overview Schema Source Related Servers Discussions Admin

Python

Local

is_feriado_nacional

Check if a given date is a Brazilian national holiday. Optionally specify a state (UF) to verify state-level holidays.

Instructions

Verifica se uma data (YYYY-MM-DD) é feriado brasileiro. UF opcional para estaduais.

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": {
      "date": "<date>"
    },
    "name": "is_feriado_nacional"
  }
}

Input Schema

Name	Required	Description	Default
`uf`	No
`date`	Yes
`municipio`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations provided, so description bears full burden. Accurately portrays the tool as a read-only check with no destructive behavior. No mention of rate limits or auth, but for a simple boolean check this is sufficient.

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?

Single short sentence, front-loaded with core purpose. Efficient and no unnecessary words. Could be slightly more structured but overall concise.

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?

Despite having an output schema, the description fails to mention the 'municipio' parameter. For a tool with 3 parameters, not documenting one is a notable gap. Behavior is otherwise clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%. Description explains 'date' (format) and 'uf' (state abbreviation) but completely omits 'municipio'. This leaves one parameter undocumented, reducing usefulness for AI agent invocation.

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?

Clearly states the tool verifies if a given date (YYYY-MM-DD) is a Brazilian holiday, with optional UF for state holidays. Distinct from siblings like listar_feriados (lists holidays) and proximo_dia_util (next business day).

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?

Specifies when to use: check a single date for holiday status. Mentions optional UF for state-specific holidays, guiding parameter usage. Lacks explicit exclusions or alternatives, but context is clear enough.

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