Skip to main content
Glama

bizcal_api__day

Is a date a business day, weekend or public holiday? Returns weekday, the holiday it falls on and the observed 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/day

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>"
    },
    "name": "bizcal_api__day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate YYYY-MM-DD
countryNoUS, GB, DE, FR or NL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / country / description
      Added value: +"US, GB, DE, FR or NL"
    • addedInput schema / properties / date / description
      Added value: +"Date YYYY-MM-DD"
    • addedInput schema / required
      Added value: +[
      +  "date"
      +]
  2. Changed2 schema fields changed
    • removedInput schema / properties / country / enum
      Removed value: -[
      -  "US",
      -  "GB",
      -  "DE",
      -  "FR",
      -  "NL"
      -]
    • removedInput schema / properties / date / description
      Removed value: -"Date YYYY-MM-DD."
  3. Changed2 schema fields changed
    • addedInput schema / properties / country / enum
      Added value: +[
      +  "US",
      +  "GB",
      +  "DE",
      +  "FR",
      +  "NL"
      +]
    • addedInput schema / properties / date / description
      Added value: +"Date YYYY-MM-DD."
  4. 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"
      -}
  5. 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"
      -}
  6. 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"
      -]
  7. 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"
      +]
  8. 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 return shape, the per-call price, the payment chain and mechanism, and the HTTP endpoint. It stops short of describing failure behavior or what happens when country is omitted, which matters for a paid call.

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?

Three tight sentences: the question and return fields come first, then cost, then transport. Nothing is repeated and no sentence is filler.

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?

There is no output schema, and the description compensates by enumerating the returned fields, plus it covers the unusual payment requirement an agent must satisfy before calling. The remaining gap is the unspecified default for the optional country parameter.

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 description coverage is 100%, so the date format and the country value list are already documented in the schema. The description adds no meaning beyond that – notably it does not say whether country defaults and to what, which is the one ambiguity the schema leaves open.

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 precise, specific question – whether a given date is a business day, weekend, or public holiday – and names the return fields (weekday, holiday, observed date). That is enough for an agent to tell it apart from range-oriented siblings like bizcal_api__between and bizcal_api__workdays, though no sibling is named explicitly.

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 only implied: a single-date classification clearly belongs here rather than in the range or batch siblings, but the description never says when to prefer bizcal_api__between, bizcal_api__workdays, or bizcal_api__batch, nor does it state prerequisites (e.g., whether country must be supplied).

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