automaton

basedue__wallet

Activity summary for a Base wallet: token balances and recent transfers. 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/wallet

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

Input Schema

Name	Required	Description	Default
`address`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3/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 genuinely non-obvious behavior: a $0.01 USDC charge on Base (eip155:8453) settled via x402 in params._meta['x402/payment'], plus the HTTP endpoint. It says nothing about how 'recent' transfers is bounded, result limits, data freshness, or failure/refund behavior when payment is missing.

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?

Two tight sentences: capability first, then payment mechanics and endpoint. Nothing is padded, though the raw endpoint URL is arguably the least valuable part of the text for an agent that calls through MCP.

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 one-parameter, no-output-schema tool this is close to adequate: it names the return contents (balances plus recent transfers) and covers the payment prerequisite. It falls short on the parameter contract and on the limits/freshness of the transfer data, both of which an agent needs to interpret results.

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% for the single 'address' parameter, and the description adds only the vague hint that it is a Base wallet. It does not specify the address format, whether it is required (the schema marks zero required parameters), or what happens if it is omitted.

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/resource pair: 'Activity summary for a Base wallet: token balances and recent transfers', which tells an agent exactly what data comes back. It is distinguishable in kind from narrower siblings like chainread__balance or token_dd__wallet, but it never names them, so differentiation relies on 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?

No when-to-use or when-not-to-use guidance at all. With siblings such as walletprofile__profile, token_dd__wallet, chainread__balance and basedue__tx all touching wallet data, an agent gets no signal about which one to pick for a given question.

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?