Skip to main content
Glama

x402-next-business-day

Next Business Day: Returns the ISO timestamp of the next Monday-to-Friday day after the given 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-next-business-day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / date / description
      Removed value: -"Date to process"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the return type (ISO timestamp), the business-day rule (Monday-to-Friday, implying no holiday calendar), and the payment model (5 free trial calls per signed wallet), which is genuinely useful context. It says nothing about behavior when the date argument is omitted, invalid input handling, or timezone assumptions.

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?

A single front-loaded sentence delivers purpose, output type, and the business-day rule, followed by a short pricing note. The free-trial/emoji tail is marketing rather than functional text, but it is brief and does convey the wallet-gated access model.

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?

With no annotations and no output schema, the description is the only documentation. It covers purpose, return type, and the weekday rule, but omits the date format, the default when the optional parameter is missing, and timezone handling, leaving meaningful gaps for a date-arithmetic tool.

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 0% for the single 'date' parameter, so the description must compensate. It only says 'after the given date', leaving the accepted format (ISO 8601? epoch?) and the behavior when the parameter is omitted (it is not required) unspecified, so it only partially fills the gap.

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: it returns the ISO timestamp of the next Monday-to-Friday day after a given date. That is precise, but it does not distinguish itself from the very close sibling x402-next-weekday (or x402-add-business-days), which an agent would have to disambiguate on its own.

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, no statement of when not to use it, and no reference to alternatives such as x402-next-weekday or x402-is-business-day. The only implied context is 'after the given date', which is a restatement of the mechanic rather than routing advice.

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