Skip to main content
Glama
Sign In
grid402-mcp

grid402-mcp

by oliveiratc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

grid402_holidays

Retrieve official Brazilian national holidays and bank closure dates from ANBIMA and Febraban, including calculated movable holidays for a chosen year.

Instructions

Consulta o calendário oficial de feriados nacionais e dias sem expediente bancário (ANBIMA e Febraban) com cálculo de feriados móveis.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "grid402_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoAno calendário de 4 dígitos entre 1900 e 2100 (ex: 2026). Se omitido, consulta o ano corrente.
payment_tx_hashNoHash opcional de transação na Base Mainnet comprovando o pagamento de 0.0005 USDC caso não utilize liquidação automática.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add real value by disclosing the data sources (ANBIMA/Febraban) and that movable holidays are computed rather than looked up, but it says nothing about the paid nature of the tool (0.0005 USDC per the schema), whether a year is required, or what the response looks like. For a tool with zero annotation coverage, that leaves meaningful behavioral gaps.

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?

A single well-formed sentence with the resource and scope front-loaded and no filler. It is appropriately sized, though its brevity comes at the cost of the routing and behavioral detail noted elsewhere.

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?

With only two optional parameters, no output schema, and full schema coverage, the description covers the core purpose and data provenance adequately. The notable omission is that payment/settlement behavior and the overlap with grid402_workdays are left entirely to the caller to discover.

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 100%, and the year parameter already documents its 1900-2100 range and the current-year default; the payment_tx_hash parameter explains the USDC payment proof itself. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ('Consulta o calendário oficial de feriados nacionais e dias sem expediente bancário') and names the authoritative sources (ANBIMA, Febraban) plus the movable-holiday calculation. However, it never distinguishes itself from the closely related sibling grid402_workdays, which plausibly covers business-day logic, so an agent must guess at the boundary.

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 only implied: an agent can infer it should call this when it needs holiday dates rather than weekday counts. There is no explicit when-to-use/when-not-to-use statement and no mention of grid402_workdays as the alternative for business-day calculations, which is the most likely confusion given the sibling set.

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