brasil-mcp-essentials

Official

Overview Schema Source Related Servers Discussions Admin

proximo_dia_util

Calculate the next business day after a specified date, automatically skipping weekends and Brazilian holidays. Optionally include the given date itself or specify a state (UF) for regional holidays.

Instructions

Retorna o próximo dia útil após uma data. Pula fins de semana e feriados.

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": "proximo_dia_util"
  }
}

Input Schema

Name	Required	Description	Default
`uf`	No
`date`	Yes
`include_today`	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.6/5.0

Behavior3/5

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

With no annotations, the description carries the burden. It discloses that weekends and holidays are skipped, but does not clarify behavior for input dates that are already business days (likely returns the same day, hinted by 'include_today' parameter) or specify the holiday calendar used.

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?

The description is extremely concise with two short sentences, front-loading the main action and behavior. No unnecessary words.

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?

Given the tool has an output schema and 3 parameters, the description covers the core purpose but leaves out parameter details and edge cases. It is adequate but not fully complete.

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%, yet the description fails to explain the 'uf' and 'include_today' parameters. The 'date' parameter is mentioned implicitly ('após uma data'), but no additional semantics are provided for the other two parameters.

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?

The description clearly states the verb 'retorna' (returns) and the resource 'próximo dia útil' (next business day), specifying that weekends and holidays are skipped. This distinguishes it from sibling tools like 'listar_feriados' or 'is_feriado_nacional'.

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?

The description implies usage when needing the next business day after a given date, but does not explicitly mention when not to use it or list alternatives. It relies on the agent's understanding of context.

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