Skip to main content
Glama

grid402_workdays

Read-onlyIdempotent

ANBIMA banking business-day count and D+N projection between dates (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_workdays"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOptional number of business days to add to start_date.
end_dateNoOptional end date in YYYY-MM-DD format.
start_dateNoStart date in YYYY-MM-DD format.
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. Changed3 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Optional number of business days to add to start_date."
    • addedInput schema / properties / end_date / description
      Added value: +"Optional end date in YYYY-MM-DD format."
    • addedInput schema / properties / start_date / description
      Added value: +"Start date in YYYY-MM-DD format."
  2. First observed

TDQS

B3.3/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 beyond that with the cost model (0.0050 USDC / 1 credit), which signals a paid metered call. It does not disclose what happens when both end_date and days are supplied, or what the default behavior is when no parameters are given.

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?

One sentence, front-loaded with the core capability and appended with the pricing constraint. No filler, no restatement of the tool name.

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?

All parameters are optional and there is no output schema, so the description should at least sketch the two operating modes and what a call returns. It implies counting and projection but leaves the mode-selection and default behavior unspecified for a paid tool.

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 all four parameters are already documented, and 'between dates' / 'D+N projection' loosely maps to the start_date/end_date/days triple. The description adds no clarification on precedence between end_date and days, nor on the payment_tx_hash authorization flow beyond the schema text. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific computation (ANBIMA banking business-day count and D+N projection between dates), which is far more informative than the opaque tool name 'grid402_workdays'. The ANBIMA calendar qualifier implicitly separates it from a generic holiday-calendar sibling, though no sibling is named explicitly.

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 guidance, no stated alternative (e.g. grid402_holidays for pure holiday lookups), and no explanation of which mode to pick. An agent must infer that this tool counts business days or projects D+N, but nothing tells it when this tool is the right choice over its siblings.

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