Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

tool_wallet_profile

[x402 paid: $0.002 USDC on Base] Base wallet profile: native ETH + USDC balances, nonce and activity level in one response. tools/call returns the live payment challenge.

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

Input Schema

NameRequiredDescriptionDefault
addressNoexample: 0x6d7488e60127480D0Dc517AE92c2f39258d5B631

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden and does partially meet it: it discloses the paid x402 gate, the exact price and chain, and that tools/call returns the live payment challenge rather than data. It does not state that this is a read-only operation, what happens on an invalid or unknown address, or whether the payment challenge must be satisfied before any content is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense, front-loaded sentences: the pricing and chain come first, then the returned fields, then the payment-challenge behavior. No filler, though the phrase "tools/call returns the live payment challenge" is protocol jargon that could be phrased more plainly for an agent deciding whether it must handle a 402 response.

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

Completeness3/5

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

Since no output schema exists, the description correctly enumerates the returned fields (ETH balance, USDC balance, nonce, activity level), which is the right compensation. It is still incomplete for a paid tool: the payment flow is mentioned but not described end-to-end, and the optional-address behavior is unaddressed.

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 description coverage is 100% and the single address parameter already carries a concrete example, so the schema does the heavy lifting. The description adds no meaning beyond it — notably it does not explain that address is optional (required count is 0) or what the tool does when it is omitted, which is the one genuinely ambiguous parameter question.

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 resource and scope: a Base wallet profile returning native ETH and USDC balances, nonce, and activity level in one response. That is materially more informative than the name alone. It does not, however, distinguish this tool from the sibling listed as 'wallet-profile', so an agent cannot tell whether they are duplicates or differ in depth.

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?

There is no explicit when-to-use guidance and no named alternative to route to. The only selection-relevant signal is the payment precondition ("[x402 paid: $0.002 USDC on Base]"), which tells the agent a cost exists but not when this tool is the right choice versus wallet-profile or the token-inspection siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources