Skip to main content
Glama

bizcal_api__add

Add N business days to a date in one country, skipping that country's weekends and public holidays (the same math as a net-terms due date). 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/add

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": {
      "date": "<date>",
      "days": "<days>"
    },
    "name": "bizcal_api__add"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesStart date YYYY-MM-DD
daysYesBusiness days to add
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 / date
      Added value: +{
      +  "description": "Start date YYYY-MM-DD",
      +  "type": "string"
      +}
    • addedInput schema / properties / days
      Added value: +{
      +  "description": "Business days to add",
      +  "type": "string"
      +}
    • removedInput schema / properties / symbols
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "date",
      +  "days"
      +]
  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 / days
      Removed value: -{
      -  "type": "number"
      -}
    • removedInput schema / properties / start
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / symbols
      Added value: +{
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • removedInput schema / properties / country / enum
      Removed value: -[
      -  "US",
      -  "GB",
      -  "DE",
      -  "FR",
      -  "NL"
      -]
    • removedInput schema / properties / date
      Removed value: -{
      -  "type": "string"
      -}
    • changedInput schema / properties / days / type
      Previous value: -"integer"New value: +"number"
    • addedInput schema / properties / start
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "date",
      -  "days"
      -]
  4. Changed3 schema fields changed
    • addedInput schema / properties / country / enum
      Added value: +[
      +  "US",
      +  "GB",
      +  "DE",
      +  "FR",
      +  "NL"
      +]
    • addedInput schema / properties / days
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / required
      Added value: +[
      +  "date",
      +  "days"
      +]
  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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the price ($0.01/call), the payment mechanism (x402 via params._meta['x402/payment']), the network (eip155:8453), and the HTTP endpoint. It omits what happens if country is omitted and what the failure modes are, which keeps it from a 5.

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?

Two compact sentences: the operation is front-loaded, and the payment/endpoint logistics follow. Every clause carries information an agent needs, with no filler or repetition of the name.

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 3-parameter, no-output-schema tool, the description covers the operation, cost, and payment path well, but never says what the tool returns (presumably a resulting date) or the default country. An agent knows how to pay and call it, but not precisely what to expect back.

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 baseline is 3; the description earns an extra point by explaining what 'business days' means operationally for the country parameter (skipping that country's weekends and public holidays). It still does not state a default when country is omitted, but the schema supplies the allowed values.

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: 'Add N business days to a date in one country', with the semantic clarification that weekends and public holidays are skipped. It does not explicitly contrast itself with close siblings such as bizcal_api__between (day counting) or bizcal_api__workdays, so an agent must infer the boundary, but the core operation is unambiguous.

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?

The net-terms due-date analogy gives useful context for when this tool fits, but there is no explicit when-not guidance and no mention of the sibling tools that handle counting between dates, listing workdays, or settling on a holiday. Usage is implied rather than prescribed.

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