Skip to main content
Glama

bizcal_api__workdays

Business days between two dates net of public holidays, with the list of weekday holidays skipped. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/bizcal-api/workdays

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

Input Schema

NameRequiredDescriptionDefault
endYesEnd date YYYY-MM-DD
startYesStart date YYYY-MM-DD
countryNoUS, GB, DE, FR or NL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / amount
      Removed value: -{
      -  "type": "number"
      -}
    • removedInput schema / properties / base
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "US, GB, DE, FR or NL",
      +  "type": "string"
      +}
    • addedInput schema / properties / end
      Added value: +{
      +  "description": "End date YYYY-MM-DD",
      +  "type": "string"
      +}
    • addedInput schema / properties / start
      Added value: +{
      +  "description": "Start date YYYY-MM-DD",
      +  "type": "string"
      +}
    • removedInput schema / properties / symbols
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "start",
      +  "end"
      +]
  2. Changed5 schema fields changed
    • addedInput schema / properties / amount
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / base
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / country
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / symbols
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / year
      Removed value: -{
      -  "type": "number"
      -}
  3. Changed5 schema fields changed
    • removedInput schema / properties / country / enum
      Removed value: -[
      -  "US",
      -  "GB",
      -  "DE",
      -  "FR",
      -  "NL"
      -]
    • removedInput schema / properties / end
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / start
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / year
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "start",
      -  "end"
      -]
  4. Changed5 schema fields changed
    • addedInput schema / properties / country / enum
      Added value: +[
      +  "US",
      +  "GB",
      +  "DE",
      +  "FR",
      +  "NL"
      +]
    • removedInput schema / properties / date
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / end
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / start
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "start",
      +  "end"
      +]
  5. Changed3 schema fields changed
    • removedInput schema / properties / countries
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / country
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / days
      Removed value: -{
      -  "type": "string"
      -}
  6. Changed6 schema fields changed
    • addedInput schema / properties / countries
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / country
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / date
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / days
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / end
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / start
      Removed value: -{
      -  "type": "string"
      -}
  7. Changed7 schema fields changed
    • removedInput schema / properties / country / description
      Removed value: -"US federal, UK England & Wales, Germany, France or Netherlands national holidays"
    • removedInput schema / properties / country / enum
      Removed value: -[
      -  "US",
      -  "GB",
      -  "DE",
      -  "FR",
      -  "NL"
      -]
    • removedInput schema / properties / end / description
      Removed value: -"YYYY-MM-DD"
    • removedInput schema / properties / end / format
      Removed value: -"date"
    • removedInput schema / properties / start / description
      Removed value: -"YYYY-MM-DD"
    • removedInput schema / properties / start / format
      Removed value: -"date"
    • removedInput schema / required
      Removed value: -[
      -  "country",
      -  "start",
      -  "end"
      -]
  8. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"US federal or UK England & Wales holidays"New value: +"US federal, UK England & Wales, Germany, France or Netherlands national holidays"
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "US",
      -  "GB"
      -]New value: +[
      +  "US",
      +  "GB",
      +  "DE",
      +  "FR",
      +  "NL"
      +]
  9. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add real operational context: it discloses the $0.01 USDC-on-Base cost, the x402 payment path in params._meta["x402/payment"], and the HTTP endpoint. It does not cover error behavior, whether the country parameter has a default, or how the holiday calendar is sourced, which keeps it below 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?

Two sentences, front-loaded with the core purpose followed by payment and transport details, with no filler. The raw HTTP URL is arguably redundant for an MCP caller but is defensible for x402 clients.

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, no-annotation, no-output-schema tool, the description covers purpose and payment mechanics but leaves the return value only implied ('the list of weekday holidays skipped') and says nothing about country defaults or invalid-input handling. Adequate, with clear gaps.

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%, so start, end, and country are already documented with formats and allowed values. The description only adds the notion of holiday exclusion, and does not say whether country is optional-by-default or which calendar applies when it is omitted. Baseline 3 is appropriate.

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 verb and resource: count business days between two dates, excluding public holidays, and return the skipped weekday holidays. That is materially clearer than the bare name. It stops short of a 5 because the very close sibling bizcal_api__between (presumably calendar-day counting) is never named, so the agent must infer the distinction.

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 explicit when-to-use or when-not-to-use guidance and no reference to alternatives such as bizcal_api__between, bizcal_api__day, or bizcal_api__batch. The reader must infer the use case purely from the phrase 'business days between two dates'.

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