automaton

basedue__allowance

ERC-20 allowance check between an owner and spender on Base. 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/allowance

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

Input Schema

Name	Required	Description	Default
`owner`	No
`token`	No
`spender`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026
- addedInput schema / properties / spender
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / token
```
Added value: +{
+  "type": "string"
+}
```
Changed2 schema fields changedNov 6, 2026
- removedInput schema / properties / spender
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / token
```
Removed value: -{
-  "type": "string"
-}
```
Changed3 schema fields changedNov 3, 2026
- addedInput schema / properties / owner
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / size
```
Removed value: -{
-  "type": "number"
-}
```
- addedInput schema / properties / spender
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 3, 2026
- removedInput schema / properties / owner
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / size
```
Added value: +{
+  "type": "number"
+}
```
- removedInput schema / properties / spender
```
Removed value: -{
-  "type": "string"
-}
```
Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / owner
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / spender
```
Added value: +{
+  "type": "string"
+}
```
AddedNov 2, 2026

TDQS

C2.9/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 behavioral burden. It usefully discloses the $0.01 USDC price, x402 payment requirement via params._meta, and HTTP endpoint, but it does not state that the operation is read-only, how missing parameters are handled, or what the result looks like.

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?

The description is short and front-loads the core purpose before the payment and HTTP details. It is efficient overall, though the raw endpoint line is less valuable to an agent than missing parameter or return-value guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid read tool with no annotations, no output schema, and fully undocumented parameters, the description is incomplete. It explains cost and payment well but omits what allowance value is returned, how decimals or token contracts are handled, and what happens when optional parameters are omitted.

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 description coverage is 0%, so the description must explain the three parameters. It names owner and spender only in passing and never mentions the token parameter, address formats, or which chain contracts are expected, leaving most parameter meaning undocumented.

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 clearly states a specific verb and resource: an ERC-20 allowance check between an owner and spender on Base. It is much more specific than a generic token lookup, but it does not explicitly distinguish itself from close siblings such as txpreflight__allowance or basedue__approvals.

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 guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The purpose sentence implies a use case, but the description does not help an agent choose between this and similar allowance or approval tools.

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?