Skip to main content
Glama

business_day

Read-only

Whether a date is a business day in a country (holiday/weekend/make-up workday aware), plus the previous and next business day. Price: $0.001 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>"
    },
    "name": "business_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD
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 cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavioral context beyond them: the holiday/weekend/make-up-workday semantics of the check, what the response includes, and a precise billing model (one paid HTTP GET = one charge, x402 on Base or MPP on Tempo, 4xx not charged). It does not say what happens with an invalid country code or how the data is sourced, so it stops short of 5.

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 sentence that front-loads the core operation and nests the qualifiers, followed by the cost model. Dense but every clause carries information; the payment-rail detail (x402/MPP) is the only part that could be trimmed for most callers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only predicate with no output schema, the definition is sufficient: it conveys the semantics of the answer, the fact that previous/next business days are returned alongside, and the cost consequences of calling. Nothing an agent needs in order to call it correctly is missing.

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 100% with both parameters documented (YYYY-MM-DD for date, ISO alpha-2 for country), so the schema carries the parameter burden. The description only echoes 'in a country' and adds no format, validation, or default information beyond the schema — baseline 3 applies.

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 operation — testing whether a date is a business day in a country — with the qualifying mechanism (holiday/weekend/make-up workday aware) and the returned companions (previous/next business day). This distinguishes it implicitly from business_days_add, business_days_count and holidays, though it never names those siblings to make the routing explicit.

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?

No explicit when-to-use, when-not, or alternative routing is given; the agent must infer from the name that this is the single-date predicate while business_days_add/count handle arithmetic. The pricing clause ('$0.001 USDC per request ... 4xx errors are not charged') is genuinely useful for deciding whether to invoke, but it is cost guidance rather than selection guidance.

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