automaton

bizcal_api__compare

Compare a settlement or due date across several countries at once and return each country's date plus the worst case. 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/compare

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

Input Schema

Name	Required	Description
`date`	Yes	Start date YYYY-MM-DD
`days`	Yes	Business days to add
`countries`	Yes	Comma-separated countries

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 9, 2026

removedInput schema / properties / amount

Removed value: -{
-  "type": "number"
-}

removedInput schema / properties / base

Removed value: -{
-  "type": "string"
-}

addedInput schema / properties / countries

Added value: +{
+  "description": "Comma-separated countries",
+  "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",
+  "countries"
+]

Changed6 schema fields changedNov 2, 2026
- addedInput schema / properties / amount
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / base
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / countries
```
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"
+}
```
AddedNov 2, 2026

TDQS

A4.1/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 so well: it discloses cost ($0.01 per call), payment currency and chain (USDC on Base, eip155:8453), the payment channel (params._meta["x402/payment"]), the transport (HTTP GET) and the endpoint URL. What is missing is failure behavior (what happens on unpaid calls) and a precise definition of 'worst case'.

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?

Purpose is front-loaded in the first clause and the cost/transport details follow compactly with no filler. The single dense sentence packing price, chain id, payment path and URL is slightly heavy but every element is operational.

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 describing the return shape (per-country date plus worst case). With no annotations it also supplies payment and transport metadata. Only the semantics of 'worst case' and acceptable country formats remain underspecified.

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 three documented parameters set the baseline at 3. The description goes beyond the schema by documenting a payment field that does not appear in the input schema at all, which is meaningful for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (compare), a specific resource (settlement or due date), and the scope (across several countries at once), then names the return shape (each country's date plus the worst case). That combination lets an agent distinguish it from single-country siblings such as bizcal_api__settle or bizcal_api__between without opening schemas.

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 phrase 'across several countries at once' implies the multi-country scenario versus single-date siblings, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that comparison across jurisdictions is what selects this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All automaton tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?