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

mcp-server-brasil

by vicgamelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Feriados nacionais

feriados_nacionais
Read-onlyIdempotent

Retrieve Brazil's national holidays for a given year, including Carnaval, Good Friday, and Corpus Christi, to plan schedules and deadlines.

Instructions

Feriados nacionais de um ano (inclui Carnaval, Sexta-feira Santa e Corpus Christi).

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": {
      "ano": "<ano>"
    },
    "name": "feriados_nacionais"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety behavior is covered. The description adds domain-specific inclusion details (Carnaval, Sexta-feira Santa, Corpus Christi) that help an agent understand what counts as a national holiday, though it does not discuss return format or year handling.

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 front-loaded sentence with no redundant wording; the parenthetical inclusion list is compact and informative.

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 one-parameter lookup with an output schema and safety annotations, the description covers the resource and notable holiday inclusions. The main gap is the lack of year-format guidance, but overall it is sufficient for correct invocation.

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% and the single required parameter 'ano' has only a title in the schema. The description's phrase 'de um ano' merely restates that the parameter is a year and adds no format, range, or validation detail.

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 names the resource (national holidays) and scopes it to a single year, and it explicitly lists movable holidays included (Carnaval, Sexta-feira Santa, Corpus Christi). It does not explicitly contrast with sibling dias_uteis, so it is clear but lacks sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The intended use is only implied by the resource name.

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