Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

x402node_time_business-days

Calculate the number of business days between two dates, excluding weekends. Use this for workday counts and date arithmetic without holiday data.

Instructions

Business days calculator / working days between dates / weekdays counter / exclude weekends / workday count / business day arithmetic. Count business days (Mon-Fri) between two dates, separating weekend days. No holiday data, just weekend exclusion.

Price: unknown on Base (auto-paid in USDC).

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": {
      "end": "<end>",
      "start": "<start>"
    },
    "name": "x402node_time_business-days"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd date YYYY-MM-DD (required)
startYesStart date YYYY-MM-DD (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so the description must disclose behavior. It states the tool does not include holiday data, which is important. However, it does not mention any other behavioral traits (e.g., error handling, edge cases).

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 description is redundant ('business days calculator / working days between dates / weekdays counter') and includes an irrelevant pricing line. It could be more concise.

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 simple tool with no output schema, the description covers the core function and a key limitation. However, it does not specify the output format (e.g., returns a number), which would help the agent interpret results.

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 description coverage is 100%, and the description does not add new meaning beyond what the schema provides. It repeats the date format but with no extra constraints or examples.

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 clearly states it calculates business days between dates, excluding weekends, with multiple synonyms reinforcing the purpose. It distinguishes itself from sibling time tools like time_duration.

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?

The description notes that it only excludes weekends (no holidays), which hints at limitations but does not explicitly mention when to use alternatives. It provides clear context but lacks exclusions.

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

Deploy Server

Other Tools