GadgetHumans API Hub

business_days

Count business days between two dates, or add N business days to a date. Pure CPU, instant. Use for SLAs and settlement dates.

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

Input Schema

Name	Required	Description
`add`	No	Business days to add
`end`	No	End date
`start`	Yes	Start date

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed4 schema fields changedNov 3, 2026

addedInput schema / properties / add

Added value: +{
+  "description": "Business days to add",
+  "type": "integer"
+}

addedInput schema / properties / end

Added value: +{
+  "description": "End date",
+  "type": "string"
+}

addedInput schema / properties / start

Added value: +{
+  "description": "Start date",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "start"
+]
```

AddedNov 2, 2026

TDQS

A3.9/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 behavioral burden. It usefully discloses that the tool is pure CPU and instant, but it omits key behavior such as weekend/holiday handling, inclusive versus exclusive end dates, accepted date formats, and return shape.

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?

The description is two tightly written sentences with no wasted wording. The core operations are front-loaded before the performance note and use cases.

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?

The tool is simple and its parameters are fully documented in the schema, but there is no output schema and the description does not explain return types or critical business-day rules. It is adequate but leaves meaningful ambiguity for an agent invoking it.

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 the baseline is 3, but the description adds value by mapping parameter roles to modes: start plus end for counting, and start plus add for date addition. It still does not explicitly discuss optionality or interactions beyond that mode mapping.

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?

The description states two specific operations, counting business days between two dates and adding N business days to a date, with the exact resource named. This clearly distinguishes it from generic date arithmetic tools such as date_calc.

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

Usage Guidelines3/5

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

It gives concrete usage contexts, SLAs and settlement dates, which implies when the tool is appropriate. However, it does not state when not to use it, name alternatives like holidays or date_calc, or clarify assumptions around weekends versus holiday calendars.

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

All GadgetHumans API Hub 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.