Skip to main content
Glama

business_days_add

Read-only

Date that is N business days after (or before, if negative) a start date in a country. Typical use: T+2 settlement, SLA and filing deadlines. Price: $0.002 USDC per request (fixed; one paid HTTP GET = one charge; x402 exact on Base or MPP on Tempo; 4xx errors 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>",
      "date": "<date>",
      "days": "<days>"
    },
    "name": "business_days_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesStart date YYYY-MM-DD
daysYesInteger -260..260
countryYesISO alpha-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: a fixed $0.002 USDC charge per request, one paid HTTP GET equals one charge, supported payment rails, and that 4xx errors are not billed. That is real cost and failure-mode information not present in structured fields.

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?

Two sentences, with the computational semantics front-loaded ahead of the pricing details, and no filler. The pricing parenthetical is dense with rail/payment jargon, but each clause carries information an agent needs before calling a paid endpoint.

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, read-only computation with no output schema, the description covers the core semantics, edge case (negative offset), and cost model. The main remaining gap is that it never states the return value's shape or that the country determines which holiday calendar is applied, which matters since no output schema exists to fill that in.

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. The description earns above baseline by explaining the sign convention for 'days' ('or before, if negative'), which the schema only expresses as a numeric range of -260..260, and by tying 'country' to the holiday-calendar selection implied by 'business days'.

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?

The description gives a specific computed result: a date N business days after (or before, with a negative N) a start date in a given country. That is a clear verb+resource statement an agent can act on. It does not name its siblings (business_day, business_days_count), so differentiation relies on the agent inferring from the tool names, which keeps it from 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 Guidelines3/5

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

'Typical use: T+2 settlement, SLA and filing deadlines' gives concrete usage contexts, which is better than nothing. However, it offers no when-not guidance and never points to business_day or business_days_count as alternatives, so the agent must infer the boundary between adding days, counting days, and testing a single date.

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