automaton

bizcal_api__settle

Invoice or trade date plus N business days = the exact due or settlement date that skips weekends and public holidays, for one or many countries, with the worst case across them. Use days=30 for net-30, days=2 for T+2. 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/settle

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

Input Schema

Name	Required	Description
`date`	Yes	Invoice or trade date YYYY-MM-DD
`days`	Yes	Business days to add: 30 for net-30, 2 for T+2
`countries`	No	Comma-separated, e.g. US,GB

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 9, 2026

addedInput schema / properties / countries / description
```
Added value: +"Comma-separated, e.g. US,GB"
```

addedInput schema / properties / date

Added value: +{
+  "description": "Invoice or trade date YYYY-MM-DD",
+  "type": "string"
+}

addedInput schema / properties / days

Added value: +{
+  "description": "Business days to add: 30 for net-30, 2 for T+2",
+  "type": "string"
+}

removedInput schema / properties / n

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

removedInput schema / properties / trade_date
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / required
```
Added value: +[
+  "date",
+  "days"
+]
```

Changed6 schema fields changedNov 2, 2026
- addedInput schema / properties / countries
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / country
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / date
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / days
```
Removed value: -{
-  "type": "number"
-}
```
- addedInput schema / properties / n
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / trade_date
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 2, 2026
- removedInput schema / properties / country / enum
```
Removed value: -[
-  "US",
-  "GB",
-  "DE",
-  "FR",
-  "NL"
-]
```
- changedInput schema / properties / days / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / required
```
Removed value: -[
-  "date",
-  "days"
-]
```
Changed3 schema fields changedNov 2, 2026
- 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"
+]
```
Changed3 schema fields changedNov 1, 2026
- removedInput schema / properties / countries
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / country
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / days
```
Removed value: -{
-  "type": "string"
-}
```
AddedOct 31, 2026

TDQS

A3.8/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 meaningful work: it discloses the cost ($0.01 per call in USDC on Base), the x402 payment path (params._meta["x402/payment"]), and the HTTP method/endpoint. An agent therefore knows it must attach payment before calling. It omits error behavior and what happens if countries is omitted.

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?

Purpose and the key computational rule are front-loaded in the first sentence, followed by a short usage example and then the payment/endpoint facts. Every sentence carries information an agent needs before calling; nothing is filler.

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 paid, three-parameter tool with no output schema and no annotations, the definition covers purpose, cost, payment and endpoint well. It never indicates what the response contains (a date string? an object per country?) or how the omitted countries parameter defaults, which leaves a real gap given there is no output schema to consult.

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, but the description adds a genuinely new semantic rule the schema never states: multiple countries are resolved by taking the worst-case date across them. The days examples duplicate the schema's own wording, which tempers the gain slightly.

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 computation: invoice/trade date plus N business days, skipping weekends and public holidays, aggregated across countries. That is a clear verb+resource. It does not, however, differentiate itself from the closely related siblings bizcal_api__add and bizcal_api__workdays, which an agent must still disambiguate on its own.

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?

'Use days=30 for net-30, days=2 for T+2' gives concrete usage framing for the settlement scenario, and 'worst case across them' explains multi-country intent. There is no explicit statement of when to prefer this over bizcal_api__add/workdays, nor any exclusion or prerequisite guidance, so usage is implied rather than directed.

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?