Skip to main content
Glama

business_days_count

Read-only

Number of business days in [start, end] inclusive (max 3 years), with the holidays that fell on weekdays. 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>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "business_days_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesYYYY-MM-DD
startYesYYYY-MM-DD
countryYesISO alpha-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond annotations: fixed price, payment protocols, one-charge-per-request semantics, and the fact that 4xx errors are not charged. It also discloses the maximum 3-year range and inclusive boundaries.

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 purpose and range constraint are front-loaded, followed by concise pricing and billing details. Every sentence carries operational information without wasteful repetition.

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?

With no output schema, the description adequately explains that the result is a business-day count plus weekday holidays. It covers limits, pricing, and return content, though the exact shape of the returned holiday data is not specified.

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 schema already explains the parameter formats. The description still adds useful semantics: the interval is inclusive and capped at 3 years, which affects how start and end must be supplied.

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 states a specific computation: count of business days in an inclusive date range, plus weekday holidays. It is clearly distinct from a single-day or date-add tool in practice, though it does not explicitly name the sibling alternatives.

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?

Usage is implied by the range-counting description and the 'max 3 years' limit. However, it does not explicitly say when to use this instead of business_day, business_days_add, or holidays.

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