Skip to main content
Glama
Sign In
mcp-server-brasil

mcp-server-brasil

by vicgamelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Contar dias úteis

dias_uteis
Read-onlyIdempotent

Calculate business days between two dates, excluding weekends and Brazilian national holidays.

Instructions

Quantidade de dias úteis entre duas datas (inclusive), descontando fins de semana e feriados nacionais. Não considera feriados estaduais/municipais.

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": {
      "inicio": "<inicio>",
      "fim": "<fim>"
    },
    "name": "dias_uteis"
  }
}

Input Schema

NameRequiredDescriptionDefault
fimYes
inicioYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 adds genuinely useful behavioral detail beyond that: the interval is inclusive and the holiday set is limited to national holidays, which directly affects the computed result.

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?

Two short sentences, front-loaded with the core operation and followed by the key scope caveat. No wasted wording.

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-date calculation with an output schema present, the description covers the essential semantics (inclusivity, holiday scope). Only minor gaps remain around date input format.

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 0%, so the description must compensate. It clarifies that the range is inclusive, which is real semantic value, but it does not explain the date format or ordering expectations for inicio/fim beyond what the schema's format:date hints at.

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?

The description states a specific operation: counting business days between two dates, inclusive, excluding weekends and national holidays. It clearly delimits scope by noting state/municipal holidays are not considered, though it does not explicitly name a sibling tool to contrast with.

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 implied by the scope statement (national holidays only), which helps an agent decide when the result is appropriate, but there is no explicit when-to-use/when-not guidance or reference to alternatives such as feriados_nacionais.

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

Deploy Server

Other Tools