Skip to main content
Glama
Sign In

xportalx

by io.github.virgen101
OverviewDiscussionsAdmin

get_wallet_balance

Check the balance of your custodial wallet. FREE - no payment required. Returns ETH and USDC balances on Base network.

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": {
      "owner_wallet": "<owner_wallet>"
    },
    "name": "get_wallet_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
owner_walletYesYour signing wallet address (0x...) to look up the linked custodial wallet balance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses the free nature, network, and balance types, but doesn't explicitly state it's a read-only operation or describe potential side effects (though 'check' implies none).

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 two concise sentences, immediately stating the purpose and then adding key details (free, network, balances) without any fluff.

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 single-parameter tool with no output schema, the description sufficiently covers what the tool does, what it returns, and on which network. It lacks error-handling details but the complexity is low.

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?

The input schema provides a full description of the owner_wallet parameter. The tool description adds no new semantic information beyond what the schema already states, so a baseline score of 3 is appropriate.

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 checks the balance of a custodial wallet, specifies the balances returned (ETH and USDC) and the network (Base). This distinguishes it from sibling tools like send_tokens, withdraw_wallet, and fund_wallet.

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 explicitly mentions the tool is FREE with no payment required, indicating when it's appropriate to use. While it doesn't name alternatives, the context is clear for a balance-checking task.

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

All xportalx 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