Skip to main content
Glama

bizcal_api__between

Count business days between two dates in one country, net of public holidays. 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/between

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__between"
  }
}

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. Changed6 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"
      -}
    • removedInput schema / properties / end
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / start
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / symbols
      Added value: +{
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / country / enum
      Removed value: -[
      -  "US",
      -  "GB",
      -  "DE",
      -  "FR",
      -  "NL"
      -]
    • 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.2/5.0
Behavior3/5

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

With no annotations, the description still discloses important operational facts: the $0.01 USDC-on-Base price, the x402 payment channel in params._meta, and the HTTP endpoint. It omits behaviorally critical details such as whether the endpoints are counted inclusively, whether start after end is an error, and how payment failure surfaces, which matter for a paid counting operation.

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 compact sentences, front-loading the function before payment and transport details. The payment string is dense but necessary for an agent to be able to pay; nothing is redundant.

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?

A paid tool with no output schema and no annotations needs the description to carry more weight. Pricing, payment channel and endpoint are covered, but counting-inclusivity semantics, the optional country default, and the error/failure behavior remain unexplained.

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 the parameter meanings are already documented in the schema. The description adds only the notion that a single country applies to the count; it does not clarify the effect of omitting the optional country or any default, so it does not meaningfully exceed the schema baseline.

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 ("Count business days between two dates") plus the holiday-netting scope, which is enough for an agent to recognize the operation. It does not name or distinguish itself from the near-identical sibling bizcal_api__workdays, so the boundary is left to inference.

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?

No indication of when to use this versus bizcal_api__workdays, bizcal_api__compare or bizcal_api__day, nor of preconditions such as having a funded x402 wallet. Selection between the bizcal count-style tools is entirely undisclosed.

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