Skip to main content
Glama

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

wallet-profile

[x402 paid: $0.010 USDC on Base] Base wallet profile in one call: native ETH + USDC balances, nonce, activity level. Three RPC calls replaced by one payment. 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": "wallet-profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoexample: 0x6d7488e60127480D0Dc517AE92c2f39258d5B631

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 supply important behavior absent from structured fields: it is an x402-paid tool at $0.010 USDC on Base and tools/call returns a live payment challenge, which an agent must know before invoking. However, it omits what happens when the optional address is omitted (0 required parameters), whether the call is read-only, and how payment failure surfaces — meaningful gaps for a paid endpoint.

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 compact sentences with the payment cost front-loaded in a bracketed tag, so the agent sees the pricing constraint first. 'Three RPC calls replaced by one payment' is partly promotional, but it does convey comparative value in few words.

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?

There is no output schema, so the description must cover return values, and it does list the four payload fields — that is the main completeness win. It is still thin for a paid tool: no statement about default behavior with no address, response shape details, or error/payment-challenge flow beyond one clause.

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 description need not re-document it. The description adds no meaning beyond the schema, such as what address formats or defaults apply when it is left out; baseline 3 applies.

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 resource and enumerates exactly what is returned: native ETH + USDC balances, nonce, activity level. It implicitly distinguishes itself from single-purpose siblings like erc20-balance by emphasizing 'in one call' / 'three RPC calls replaced by one, but it never names an alternative, so it stops short of full differentiation.

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

Usage Guidelines3/5

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

'Base wallet profile in one call' and 'three RPC calls replaced by one payment' imply the case where you want a consolidated snapshot rather than individual RPC/balance lookups, but usage is only implied. There is no explicit when-to-use, when-not, or named alternative, so the agent must infer the routing decision.

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