Skip to main content
Glama

Add business days to date

add-business-days-to-date
Read-onlyIdempotent

Use when you need the Canadian business day a count lands on, or to check whether a date is a business day. Moves a start date forward 0 to 260 business days on the Payments Canada calendar and names each closure day passed. $0.01 USDC on Base per answer via x402; a refusal is free.

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": {
      "start_date": "<start_date>",
      "business_days": "<business_days>",
      "calendar": "<calendar>",
      "acknowledge": "<acknowledge>",
      "freshness_tolerance": "<freshness_tolerance>"
    },
    "name": "add-business-days-to-date"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendarYes
start_dateYesa real calendar date in a year the calendar covers; it may be a weekend or a closure day
acknowledgeYes
business_daysYesbusiness days to move forward, 0 to 260; 0 moves a day that is not a business day to the next one
freshness_toleranceYesat most the ratified ceiling

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the description earns credit for the extras it adds: the 0-260 bound, the specific calendar, the fact that each closure day passed is named, and the x402 pricing with free refusals. It stops short of explaining what triggers a refusal or what those extra required parameters are acknowledging.

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?

Three sentences, front-loaded with the 'Use when' clause, with no filler. The pricing clause is unusual but legitimately earns its place as agent-relevant context; there is minor overlap between the 'check whether a date is a business day' clause and the forward-move sentence.

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?

For a tool with five required parameters, no output schema, and two opaque legal/versioning parameters, the description answers the core question but leaves notable unknowns. It partially compensates by describing the returned closure-day names, but an agent still cannot reason about 'acknowledge' or 'freshness_tolerance' before calling.

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?

The description clarifies business_days semantics ('0 moves a day that is not a business day to the next one') and identifies the calendar, which is real added meaning. But two required parameters, 'acknowledge' (enum 'no-ruling-v1') and 'freshness_tolerance' ('at most the ratified ceiling'), are completely unexplained in both schema and description, and 60% coverage leaves those gaps unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Moves a start date forward 0 to 260 business days on the Payments Canada calendar') plus a secondary use case, and the scope is narrow enough that an agent can tell it apart from siblings like compute-day-count-to-settlement or diff-two-line-lists.

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

Usage Guidelines4/5

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

'Use when you need the Canadian business day a count lands on, or to check whether a date is a business day' gives clear trigger conditions and implicitly separates the two modes. There is no explicit when-not or named alternative, which keeps it below a 5.

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