Skip to main content
Glama

grid402_holidays

Read-onlyIdempotent

ANBIMA Brazilian banking holidays calendar for a given year (0.0050 USDC / 1 credit).

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
yearNo4-digit target calendar year (e.g. 2026).
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / year / description
      Added value: +"4-digit target calendar year (e.g. 2026)."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context the annotations do not: the data source (ANBIMA) and the cost (0.0050 USDC / 1 credit). It says nothing about the shape of the returned calendar, though for a simple lookup tool that is a minor gap.

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 that states resource, scope, and price with no filler. Nothing is padded or repeated.

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 two-parameter read-only lookup with full schema coverage and annotations, the description covers source, scope, and cost adequately. The only missing element is how it relates to the neighboring workdays tool, which would help an agent choose correctly.

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%, so both parameters, including the payment/auth options, are already fully documented in the schema. The description's 'for a given year' merely restates the year parameter and adds no format or edge-case guidance, 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 names a specific resource and scope: the ANBIMA Brazilian banking holidays calendar for a given year. An agent immediately knows what data comes back (holiday dates). It does not distinguish itself from the sibling grid402_workdays, which plausibly overlaps, so it falls short of a 5.

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 explicit when-to-use guidance, no prerequisites, and no pointer to alternatives such as grid402_workdays for business-day counts. Usage is only inferable from the phrase 'for a given year'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources