Skip to main content
Glama

Business Days Calculator API - add working days, count between dates

business_days
Read-onlyIdempotent

Working-day maths with each country's (and state's) public holidays: add or subtract N business days to a date (payment terms, delivery, legal deadlines), or count business days between two dates. Custom weekend (e.g. Fri-Sat). Returns the holidays that were skipped. < 50 ms. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/business-days.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "add": 5,
      "start": "2026-12-22",
      "country": "DE"
    },
    "name": "business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNoBusiness days to add (negative = back)
endNoOr an end date YYYY-MM-DD to count business days between
startNoStart date YYYY-MM-DD (default today)
countryYesISO 3166 alpha-2 code, e.g. DE, BG, US
weekendNoWeekend weekdays, 0=Mon..6=Sun, default 5,6
subdivisionNoState/region code (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover read-only, open-world and idempotency, and the description goes well beyond them: sub-50ms latency, a free tier of 25 calls/day per IP, paid x402 pricing at $0.001 per call with a URL, and the fact that skipped holidays are returned. These are exactly the operational facts an agent needs before calling a metered external API.

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?

The core capability and mode split are front-loaded in the first sentence, with secondary facts (custom weekend, returned holidays, latency, pricing) trailing. Dense but nearly every clause carries information; the pricing URL is the only element an agent arguably doesn't need for invocation.

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 6-parameter, no-output-schema tool it covers the important ground: both modes, holiday/subdivision scoping, custom weekend support, and a partial return-value note ('returns the holidays that were skipped'). It leaves the shape of the counted-days result implicit, a minor gap given no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds the mode logic that the schema only implies per-field: 'add' means offset from a start date while 'end' switches to a between-dates count, and it illustrates a custom weekend such as Fri-Sat. That clarifies parameter interaction rather than merely restating field docs.

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?

States a concrete verb+resource pair: add/subtract N business days to a date, or count business days between two dates, with per-country/state holiday awareness and custom weekends. An agent can tell this is a working-day arithmetic tool rather than a holiday lookup. It does not explicitly name a sibling (e.g. public_holidays) to route against, so it stops 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 Guidelines4/5

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

Supplies concrete use contexts (payment terms, delivery, legal deadlines) and distinguishes the two operating modes — add/subtract N days versus count between two dates. It does not state when to prefer a different tool or note exclusions, so it is clear context without explicit alternatives.

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