automaton

basedue__estimate

Estimate the USD cost of a Base transaction given gas and calldata. 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/basedue/estimate

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "basedue__estimate"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026
- addedInput schema / properties / data
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 6, 2026
- removedInput schema / properties / amount
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / to
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / token
```
Removed value: -{
-  "type": "string"
-}
```
Changed2 schema fields changedNov 6, 2026
- addedInput schema / properties / amount
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / size
```
Removed value: -{
-  "type": "number"
-}
```
Changed3 schema fields changedNov 3, 2026
- addedInput schema / properties / size
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / token
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / tx
```
Removed value: -{
-  "type": "string"
-}
```
AddedNov 2, 2026

TDQS

B3.2/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the two things an agent most needs to know before calling: the cost ($0.01 per call in USDC on Base, eip155:8453) and the payment mechanism (x402 via params._meta["x402/payment"]). That is genuinely useful non-obvious behavior. It stops short of stating the response shape or what happens on payment failure.

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 purpose, then price and transport in a compact sequence. The raw HTTP URL is marginal value for an MCP caller, but the text is short and every other clause earns its place.

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 two-parameter estimation tool with no output schema and no annotations, the description covers payment but leaves the essential contract thin: it does not say what the estimate returns, how gas is derived when no gas field is passed, or how errors surface. It is adequate to attempt a call but not to call confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema exposes only 'to' and 'data', neither described. The description says 'given gas and calldata' — calldata plausibly maps to 'data', but 'gas' is not a parameter at all, which actively misleads. It also references an undeclared params._meta["x402/payment"] field, leaving the agent to reconcile three sources for a two-parameter tool.

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 verb and resource: 'Estimate the USD cost of a Base transaction given gas and calldata.' An agent immediately knows this is a cost-prediction tool, not a broadcaster or a gas oracle. However, it never names a sibling (basedue__gas, basedue__tx, chainread__gas all sit nearby), so differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. With siblings like basedue__gas, basedue__tx and basedue__due in the same namespace, the agent has to guess whether to call this or the gas tool to price a transaction. The phrase 'given gas and calldata' hints at inputs but does not route the agent.

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?