Agent Decision & Evidence Tools (MCP + x402)

Wallet execution evidence

wallet_balance

Read-only

Return a live native balance, exact wei, pending nonce, observed block and RPC-source evidence for a wallet on Base, Ethereum, Arbitrum, Optimism or Polygon.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No		base
`address`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	No
`chain`	No
`error`	No
`address`	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.
`sources`	No
`unknown`	No
`accepted`	No
`contract`	No
`read_only`	No
`retryable`	No
`checked_at`	No
`error_code`	No
`extensions`	No
`balance_wei`	No
`status_code`	No
`did_you_mean`	No
`native_symbol`	No
`pending_nonce`	No
`balance_native`	No
`missing_checks`	No
`observed_block`	No
`partial_evidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 6, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / address / pattern
```
Added value: +"^0x[a-fA-F0-9]{40}$"
```
removedInput schema / properties / address / title
```
Removed value: -"Address"
```
removedInput schema / properties / chain / title
```
Removed value: -"Chain"
```

removedInput schema / title

Removed value: -"wallet_balance_toolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "contract",
+        "chain",
+        "read_only",
+        "checked_at",
+        "sources",
+        "address",
+        "native_symbol",
+        "balance_wei",
+        "balance_native",
+        "pending_nonce",
+        "observed_block",
+        "receipt",
+        "extensions"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Structured result contract for wallet_balance. 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"
+    },
+    "address": {
+      "type": "string"
+    },
+    "balance_native": {
+      "type": "string"
+    },
+    "balance_wei": {
+      "type": "string"
+    },
+    "chain": {
+      "type": "string"
+    },
+    "charged": {
+      "description": "When present on an error, false means the failed result is uncharged.",
+      "type": "boolean"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "contract": {
+      "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"
+    },
+    "native_symbol": {
+      "type": "string"
+    },
+    "observed_block": {
+      "type": "integer"
+    },
+    "partial_evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "pending_nonce": {
+      "type": "integer"
+    },
+    "read_only": {
+      "type": "boolean"
+    },
+    "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"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "settled": {
+      "description": "When present on an error, false means no settlement occurred.",
+      "type": "boolean"
+    },
+    "sources": {
+      "items": {},
+      "type": "array"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "unknown": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral detail: it promises a live value, exact wei precision, pending nonce, observed block, and RPC-source evidence, giving the agent a clear picture of what the call will return.

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?

The description is a single well-structured sentence, front-loaded with the verb 'Return'. Every phrase contributes either a specific return field or a supported chain, with no filler or repetition.

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 low-complexity read-only tool with two parameters and an output schema, the description is largely complete: it lists the key return fields and supported chains. The main gap is the lack of usage routing guidance and explicit mention of the default chain behavior, though the schema covers the default.

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 needed to compensate. It mostly restates the chain enum and refers to the address as a 'wallet', adding no meaning about address normalization, default chain behavior, or how the chain parameter affects the returned evidence.

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 uses a specific verb and resource: 'Return a live native balance, exact wei, pending nonce, observed block and RPC-source evidence for a wallet.' It also enumerates the five supported chains, which clearly differentiates this tool from generic balance or data-reading tools.

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 gives no guidance on when to use this tool versus sibling tools such as rpc_read_batch, gas_estimate, tx_status, or spot_price. It provides no context like 'before transaction execution' despite the title 'Wallet execution evidence', and no exclusions or alternative selection criteria.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.