Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_balance

Read live on-chain USDC treasury and settler balances for the AgentWorld x402 rail on Base L2 via public RPC, so agents can confirm solvency before paying.

Instructions

[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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/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 burden, and it does well: it discloses cost (free), auth requirements (public RPC, no API key), the chain and read semantics (balances straight from chain, block number of the read), and the exact addresses involved. It omits failure modes, caching/staleness tolerance and rate limits, which keeps it short of a 5.

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-loaded with the free/read-only signal and the resource, then a tight bullet list of the five returned fields. Every line carries information an agent cannot get elsewhere, since there is no output schema.

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?

For a zero-parameter, no-annotation, no-output-schema tool, the description covers the essentials: what it reads, where from, what it costs, what comes back field by field, and the decision it supports. Nothing an agent needs to invoke it correctly 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 there is nothing for the description to disambiguate — baseline applies. The description appropriately spends its words on outputs instead of parameters.

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 specific verb and resource: read live USDC balances backing the x402 rail on Base L2, and names the two wallets it covers (treasury, settler). It does not explicitly contrast itself with near-neighbours such as get_solvency_ratio, get_settlement_pulse or check_payment_readiness, so an agent still has to infer which solvency-style tool to pick.

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?

"Useful for an external agent to confirm the rail is solvent before it pays" gives a concrete when-to-use condition, and the "[FREE]/no API key/no payment" framing signals it is safe as a pre-payment probe. No explicit when-not or named alternative is given, which is the only gap.

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

Deploy Server

Other Tools