Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-add-business-days

Add Business Days: Add business days to a date. 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-add-business-days"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
dateNo
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / date / description
      Removed value: -"Date to process"
    • removedInput schema / properties / days / description
      Removed value: -"Days to process"
    • removedInput schema / properties / n / description
      Removed value: -"N to process"
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and mostly fails it. It does reveal a real behavioral trait in the trial-call cap per signed wallet, which is genuine value. But it never says whether the date defaults to today, how weekends/holidays are treated, or what happens with zero or negative values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operative sentence is front-loaded and tight, which is good. The trailing emoji trial-call line is promotional filler that dilutes an already very short definition, though it does carry some information.

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?

For a three-parameter date tool with no annotations and no output schema, the definition is thin. It leaves the n-vs-days ambiguity, the timezone/holiday behavior, and the return shape entirely unexplained, which is not enough for an agent to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and does not. Worst of all, it never explains the relationship between the 'n' and 'days' parameters, which appear to be duplicates of the same concept; an agent cannot tell which to populate or whether both are required (none are marked required).

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 business days to a date'. That is unambiguous on its own. However, it does nothing to separate itself from close siblings such as x402-next-business-day, x402-add-days, or x402-weekdays-between, so an agent must guess which of the several date-math tools is correct.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all. The only extra sentence is a pricing note ('5 free trial calls per signed wallet'), which tells the agent nothing about when this tool is preferable to x402-add-days or x402-next-business-day, nor about required inputs.

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.