automaton

basedue__payee

Resolve the payment recipient and price metadata for this API. 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/payee

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026
- removedInput schema / properties / address
```
Removed value: -{
-  "type": "string"
-}
```
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

A3.6/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 load and does disclose important behavior: the call costs $0.01 USDC on Base (eip155:8453), payment is via x402 in params._meta["x402/payment"], and it is a GET HTTP endpoint. What it does not say is what the response payload looks like or whether payment is required before or after the call.

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?

Purpose is front-loaded in the first clause, followed by compact cost/payment/transport metadata. Slightly dense with the raw HTTP URL and CAIP-2 chain id, but no sentence is wasted.

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

Completeness4/5

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

For a zero-parameter, no-output-schema tool, the description covers what it returns (recipient and price metadata), what it costs, and how payment is attached. Adding the response shape or whether the payment header is mandatory would round it out.

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?

The tool takes zero declared parameters, so the baseline is 4. The description usefully notes that a payment object may be expected at params._meta["x402/payment"] even though the schema is empty, which is genuinely additive information.

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 concrete verb+resource: 'Resolve the payment recipient and price metadata'. An agent can tell this returns payout-address/pricing info, distinct from siblings like basedue__price or basedue__due. It stops short of explicitly differentiating from those similar-sounding siblings, which keeps it at 4.

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, and no mention of alternatives despite several closely named siblings (basedue__price, basedue__check, basedue__estimate). The agent must infer that this is a discovery/payment-info call rather than a pricing lookup.

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?