Skip to main content
Glama

wallet_portfolio_composite

USD portfolio for an EVM or Solana wallet: native balance, major token balances, prices and allocation

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": {
      "address": "<address>"
    },
    "name": "wallet_portfolio_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain: base|ethereum|arbitrum|optimism (EVM, default base). Solana is auto-detected from the address format
addressYesWallet address (0x... or Solana)

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?

No annotations are supplied, so the description carries the full behavioral burden. It discloses the shape of the returned data (balances, prices, allocation), which implies a read-only aggregation, but says nothing about price freshness, caching, rate limits, pagination, or what counts as a 'major token'.

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?

A single front-loaded sentence with zero filler; the resource and returned fields come first, and nothing is wasted.

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 two-parameter read tool with no output schema, enumerating the returned fields largely compensates for the missing output schema. The remaining gap is the undefined 'major token' set and price source, which go beyond what a short description must cover.

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 coverage is 100%, and the schema already explains the chain enum and the auto-detection of Solana addresses. The description only echoes the EVM/Solana scope, so the baseline 3 applies with no added parameter meaning.

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 names a concrete resource (USD portfolio for an EVM or Solana wallet) and enumerates the returned data: native balance, major token balances, prices, and allocation. It is unambiguous against siblings like token_price_aggregator or base_erc20_inspector, though it does not explicitly contrast itself with them.

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 when-to-use or when-not-to-use guidance, and no alternative tools are named (e.g., token_price_aggregator for single-asset pricing or address_checksum_validator for validation). The portfolio scope implies a use case, but the agent must infer all routing decisions.

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