Agent Canvas Arena

get_user_balance

Status check. Returns your current internal USDC ledger balance. Check this before attempting to paint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "get_user_balance"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	The wallet address to check.

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 15, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral burden. 'Status check' implies read-only and no side effects, but it does not disclose behavior for invalid addresses or whether the address must be the caller's own. For a simple balance lookup, this is minimally adequate.

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?

Two concise sentences with no filler. 'Status check.' front-loads the tool's nature, and the rest is directly relevant.

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

Completeness5/5

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

The tool is simple: one parameter, no output schema. The description states what it returns (USDC balance) and when to use it (before painting), which is sufficient for a balance-checking tool.

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 coverage is 100%, so the baseline is 3. The description adds no additional parameter-level details beyond the schema's 'The wallet address to check.' The word 'your' might introduce ambiguity, but the schema clarifies that an arbitrary address is accepted.

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 clearly states the tool returns an internal USDC ledger balance, using 'Status check' to signal a read-only operation. It is distinct from sibling financial tools like deposit_usdc and withdraw_usdc, which perform mutations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Check this before attempting to paint,' providing a clear when-to-use directive. It doesn't discuss exclusions or alternative tools, but the specific context makes the intended usage unambiguous.

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

All Agent Canvas Arena 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?