Skip to main content
Glama

Working days for a country. mode=between counts the working

business_days
Read-only

Working days for a country. mode=between counts the working days after from up to and including to (up to 5 years) and lists the public holidays skipped; mode=add gives the date that is N working days after date (up to 3,650). Weekends are Saturday and Sunday, Friday and Saturday in Israel, and Friday only in Iran and Afghanistan. Nationwide public holidays from Nager.Date; a country with no holiday data is a 404, not charged. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "country": "<country>"
    },
    "name": "business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD (mode between; counted)
dateNoStart date YYYY-MM-DD (mode add)
daysNoWorking days to add, negative to subtract, up to 3,650 in size (mode add)
fromNoStart date YYYY-MM-DD (mode between; not counted)
modeNobetween (default) or add
countryYesISO 3166 alpha-2 code, e.g. DE, US, IL

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
modeNo
sourceNo
countedNo
countryNo
checkedAtNo
weekendDaysNo
workingDaysNo
calendarDaysNo
holidaysSkippedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly and openWorld, so the description carries real weight and delivers: per-country weekend definitions, holiday data source, 404 behavior for countries without data, span caps (5 years / 3,650 days), and full pricing/payment semantics with the guarantee that failed calls are not charged.

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?

Front-loaded with purpose, then mode behavior, then calendar rules, then commercial terms — each sentence adds distinct information. The pricing sentence is long but justified since payment terms materially affect invocation decisions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema and complete parameter documentation, the description supplies exactly the remaining decision-critical context: mode contract, span limits, weekend conventions, error behavior, and cost. Nothing needed to call it correctly is missing.

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 conditional parameter semantics the schema only hints at: which date parameter belongs to which mode and whether boundaries are counted. It does not restate the ISO format, correctly leaving that to the schema.

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 resource (working days for a country) and then defines the two operational modes with exact computational semantics, including which endpoints are inclusive. An agent can distinguish mode=between from mode=add without opening the schema.

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?

The mode descriptions make the selection condition implicit but clear: use between for a counted span, add for date arithmetic. It does not explicitly name the sibling 'holidays' tool as the alternative for pure holiday listing, so exclusion guidance is absent.

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