Skip to main content
Glama
Sign In

AgentWorld

by me.agentworld
OverviewDiscussionsAdmin

get_balance

[FREE] Read the live USDC balances backing the AgentWorld x402 rail on Base L2, straight from the chain (public RPC, no API key, no payment). Returns:

  • treasury_usdc : USDC held by the payment treasury (0x367F...)

  • settler_usdc : USDC in the settlement/ops wallet (0xAB1F...)

  • usdc_contract : the USDC token contract address

  • block_number : the Base L2 block the read was taken at

  • rpc : the public RPC used Useful for an external agent to confirm the rail is solvent before it pays.

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": "get_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses cost ('[FREE]'), auth ('no API key, no payment'), and data provenance ('straight from the chain', public RPC, with block_number capturing read freshness). It stops short of failure modes, rate limits, or caching behavior.

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?

Front-loads the key qualifier '[FREE]' and the operation, then lists returned fields compactly. Every sentence earns its place and the structure makes the payload scannable.

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?

No parameters and an output schema exists, so the description need not document returns — yet it still summarises them, and it covers purpose, cost, and provenance. Nothing an agent needs to decide to call it is missing.

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 parameters, so the schema has nothing to explain and the baseline is 4. The description instead enumerates the return payload, which is parameter-adjacent but not a substitute for parameter documentation.

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?

The description states a specific verb and resource: reading live USDC balances, and pins the scope precisely to the AgentWorld x402 rail on Base L2, naming the treasury and settler wallets involved. It is clear what the tool does, though it never explicitly contrasts itself with nearby siblings such as get_solvency_ratio, get_settlement_pulse, or check_facilitator_liveness.

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?

It gives a concrete use case: 'Useful for an external agent to confirm the rail is solvent before it pays.' That tells the agent when this is relevant, but there is no exclusion or routing statement against the many related health/liveness tools in the sibling list.

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

All AgentWorld toolsInspect
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