Agent Decision & Evidence Tools (MCP + x402)

ERC-20 balance and allowance evidence

token_status

Read-only

Return an owner's token balance and optional spender allowance, including whether both satisfy a requested amount, across five EVM chains.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No		base
`owner`	Yes
`token`	Yes
`amount`	No	Exact decimal string preferred; JSON number remains accepted for backwards compatibility.
`spender`	No

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`tool`	No
`chain`	No
`error`	No
`owner`	No
`token`	No
`balance`	No
`charged`	No	When present on an error, false means the failed result is uncharged.
`message`	No
`missing`	No
`receipt`	No
`settled`	No	When present on an error, false means no settlement occurred.
`spender`	No
`unknown`	No
`accepted`	No
`chain_id`	No
`allowance`	No
`retryable`	No
`checked_at`	No
`error_code`	No
`extensions`	No
`balance_raw`	No
`status_code`	No
`did_you_mean`	No
`action_needed`	No
`would_succeed`	No
`missing_checks`	No
`blocking_reasons`	No
`partial_evidence`	No
`requested_amount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 6, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / amount / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "minimum": 0,
+    "type": "number"
+  }
+]

changedInput schema / properties / amount / default
```
Previous value: -0New value: +""
```

addedInput schema / properties / amount / description

Added value: +"Exact decimal string preferred; JSON number remains accepted for backwards compatibility."

removedInput schema / properties / amount / title
```
Removed value: -"Amount"
```
removedInput schema / properties / amount / type
```
Removed value: -"number"
```
removedInput schema / properties / chain / title
```
Removed value: -"Chain"
```
addedInput schema / properties / owner / pattern
```
Added value: +"^0x[a-fA-F0-9]{40}$"
```
removedInput schema / properties / owner / title
```
Removed value: -"Owner"
```
removedInput schema / properties / spender / title
```
Removed value: -"Spender"
```
addedInput schema / properties / token / pattern
```
Added value: +"^0x[a-fA-F0-9]{40}$"
```
removedInput schema / properties / token / title
```
Removed value: -"Token"
```

removedInput schema / title

Removed value: -"token_status_toolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "chain",
+        "chain_id",
+        "token",
+        "owner",
+        "balance_raw",
+        "balance",
+        "checked_at",
+        "note",
+        "receipt",
+        "extensions"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Structured result contract for token_status. A success satisfies the documented success branch. A domain or tool error includes error and is not a successful settlement; unpaid x402 requirements are carried by the transport wrapper.",
+  "properties": {
+    "accepted": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "action_needed": {
+      "type": "string"
+    },
+    "allowance": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "balance": {
+      "type": "string"
+    },
+    "balance_raw": {
+      "type": "string"
+    },
+    "blocking_reasons": {
+      "items": {},
+      "type": "array"
+    },
+    "chain": {
+      "type": "string"
+    },
+    "chain_id": {
+      "type": "integer"
+    },
+    "charged": {
+      "description": "When present on an error, false means the failed result is uncharged.",
+      "type": "boolean"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "did_you_mean": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "error": {
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "message": {
+              "type": "string"
+            },
+            "param": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "message"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "extensions": {
+      "additionalProperties": true,
+      "properties": {
+        "delivery-receipt": {
+          "additionalProperties": true,
+          "properties": {
+            "how_to_verify": {
+              "type": "string"
+            },
+            "issued_at": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "issuer": {
+              "type": "string"
+            },
+            "issuer_key": {
+              "type": "string"
+            },
+            "key_id": {
+              "type": "string"
+            },
+            "result_hash": {
+              "type": "string"
+            },
+            "service": {
+              "type": "string"
+            },
+            "signature": {
+              "type": "string"
+            },
+            "signed_message": {
+              "type": "string"
+            },
+            "standard": {
+              "const": "eucompliance-receipt/2",
+              "type": "string"
+            },
+            "subject": {
+              "type": "string"
+            },
+            "valid_until": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "verify_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "standard",
+            "service",
+            "subject",
+            "result_hash",
+            "issued_at",
+            "valid_until",
+            "issuer",
+            "issuer_key",
+            "key_id",
+            "verify_url",
+            "how_to_verify",
+            "signature",
+            "signed_message"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "delivery-receipt"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missing_checks": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "owner": {
+      "type": "string"
+    },
+    "partial_evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "how_to_verify": {
+          "type": "string"
+        },
+        "issued_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "issuer": {
+          "type": "string"
+        },
+        "issuer_key": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "result_hash": {
+          "type": "string"
+        },
+        "service": {
+          "type": "string"
+        },
+        "signature": {
+          "type": "string"
+        },
+        "signed_message": {
+          "type": "string"
+        },
+        "standard": {
+          "const": "eucompliance-receipt/2",
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "valid_until": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "verify_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "standard",
+        "service",
+        "subject",
+        "result_hash",
+        "issued_at",
+        "valid_until",
+        "issuer",
+        "issuer_key",
+        "key_id",
+        "verify_url",
+        "how_to_verify",
+        "signature",
+        "signed_message"
+      ],
+      "type": "object"
+    },
+    "requested_amount": {
+      "type": "string"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "settled": {
+      "description": "When present on an error, false means no settlement occurred.",
+      "type": "boolean"
+    },
+    "spender": {
+      "type": "string"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "token": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "unknown": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "would_succeed": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

AddedAug 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds some useful behavior beyond them: multi-chain scope and the threshold-comparison logic. However, it leaves ambiguity about whether 'both satisfy' means each of balance and allowance independently meets the amount, and it gives no caveat about openWorldHint=true (results depend on user-supplied external contract state). The added context is modest but non-empty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the core action ('Return an owner's token balance') and packs scope, optionality, and the comparison feature into the rest with zero filler. Every 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?

With an output schema present, return values need no explanation, and annotations cover the read-only semantics. The remaining gaps are the unnamed five chains (critical since chain is a free-form string), the ambiguous satisfaction semantics, and the absence of use-case guidance. This makes the definition partially complete but not fully self-sufficient for correct invocation.

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 description coverage is only 20% (just the amount field), so the description carries the burden of explaining parameters. It does map token, owner, spender, and amount to their roles (ERC-20 token, balance holder, allowance grantee, requested threshold), which adds meaning. But the chain parameter is left vague — 'five EVM chains' are promised yet never enumerated, and there is no enum in the schema, so an agent cannot know valid chain values beyond the default 'base'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Return'), a concrete resource (owner's token balance and optional spender allowance), and a distinguishing feature ('whether both satisfy a requested amount') that separates it from siblings like wallet_balance or contract_info. The 'across five EVM chains' scope adds further precision. No tautology or ambiguity.

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?

The description says what the tool does but gives no guidance on when to choose it over overlapping siblings such as wallet_balance, rpc_read_batch, or contract_info. There are no 'use this when' conditions, no exclusion criteria, and no mention of alternatives. An agent must infer appropriate usage entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Decision & Evidence Tools (MCP + x402) 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.