automaton

bizcal_api__batch

Run many dates at once: pass a comma-separated list of dates (max 50) for one country in a single call instead of paying per 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/batch

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": {
      "dates": "<dates>"
    },
    "name": "bizcal_api__batch"
  }
}

Input Schema

Name	Required	Description	Default
`dates`	Yes	Comma-separated dates YYYY-MM-DD, up to 50
`country`	No	US, GB, DE, FR or NL

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 9, 2026

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 / dates

Added value: +{
+  "description": "Comma-separated dates YYYY-MM-DD, up to 50",
+  "type": "string"
+}

removedInput schema / properties / symbols

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

addedInput schema / required
```
Added value: +[
+  "dates"
+]
```

Changed5 schema fields changedNov 2, 2026
- 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 / dates
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / symbols
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 2, 2026
- removedInput schema / properties / country / enum
```
Removed value: -[
-  "US",
-  "GB",
-  "DE",
-  "FR",
-  "NL"
-]
```
- removedInput schema / properties / dates / description
```
Removed value: -"Comma-separated YYYY-MM-DD dates."
```
- removedInput schema / required
```
Removed value: -[
-  "dates"
-]
```

Changed4 schema fields changedNov 2, 2026

addedInput schema / properties / country / enum

Added value: +[
+  "US",
+  "GB",
+  "DE",
+  "FR",
+  "NL"
+]

removedInput schema / properties / date

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

addedInput schema / properties / dates

Added value: +{
+  "description": "Comma-separated YYYY-MM-DD dates.",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "dates"
+]
```

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"
-}
```
Changed6 schema fields changedOct 31, 2026
- 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"
-}
```
AddedOct 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose important behavior: pricing ($0.01 per call in USDC on Base), the x402 payment mechanism in params._meta, and the HTTP endpoint. However, it says nothing about error handling, partial failures within a batch, or what the response contains, and it references a _meta payment field that is absent from the input schema.

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?

Front-loaded with the core action and limit, followed by the payment and endpoint details. Dense but every clause carries information; no 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?

Covers cost, payment, limits, and transport, which is strong for a paid batch tool. But with no output schema, the description should say what a batch response looks like (per-date results, ordering, failure behavior), and it does not.

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 both parameters are already documented. The description reinforces the 50-date cap and the one-country constraint but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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: run many dates in one call, comma-separated list, max 50, one country. The 'instead of paying per date' phrasing implicitly contrasts it with the single-date sibling (bizcal_api__day), though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditions for use: many dates, a single country, up to 50 per call, and the cost motivation. It does not explicitly say when NOT to use it or name the alternative tool for single-date or multi-country lookups.

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?