Agent Tools

business_day_add

Due-date calculator: add or subtract N business days from a date, skipping weekends and nationwide public holidays for a country (ISO code). Returns the result date and weekday, which holidays were skipped and whether the start day is a working day. For SLAs, invoice terms, shipping and legal deadlines. Price $0.001 USDC per call via x402. Example output: {"start":"2026-12-23","start_weekday":"Wednesday","start_is_business_day":true,"days":5,"result":"2026-12-31","result_weekday":"Thursday","calendar_days":8,"weekend_days_skipped":2,"holidays_skipped":[{"date":"2026-12-25","name":"Christmas Day"}],"country":"US"}

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": "<start>",
      "days": "<days>"
    },
    "name": "business_day_add"
  }
}

Input Schema

Name	Required	Description
`days`	Yes	Whole number of business days, negative to go back (max 1000)
`start`	Yes	Start date YYYY-MM-DD (not counted)
`country`	No	Optional ISO 3166 alpha-2, e.g. US

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose cost ($0.001 USDC per call via x402) and the shape of the returned data via an example, which are meaningful additions. It does not say what happens when 'country' is omitted (national holidays silently ignored?), nor how invalid or out-of-range dates behave, so the behavioral picture is good but incomplete.

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-loads purpose, then use cases, then pricing, then return example — a sensible progression with no filler sentences. The embedded JSON example is long but justified since there is no output schema, though it is heavy for a description field.

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 three-parameter computation tool with no output schema, the description supplies an illustrative return payload covering result date, weekdays, skipped weekends and named holidays — which is exactly what would otherwise be missing. The remaining gap is edge-case behavior (missing country, invalid dates, range limits beyond the schema's max).

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 coverage is 100%, so all three parameters are already documented, including the negative-to-go-back convention and the YYYY-MM-DD format. The description adds only the ISO-code framing for country, which the schema already provides — 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?

States a specific verb and resource ('add or subtract N business days from a date') plus the key modifier ('skipping weekends and nationwide public holidays for a country'), which clearly separates it from a naive day-count utility. It never names the neighboring 'business_days' or 'public_holidays' tools, so an agent must infer the boundary rather than being told it.

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?

Gives concrete use-case context ('For SLAs, invoice terms, shipping and legal deadlines'), which tells an agent when this tool is the right pick. It stops short of explicit exclusions or naming the sibling to use for plain calendar-day math or raw holiday listing.

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

All Agent Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?