Skip to main content
Glama

Get wallet portfolio

get_wallet_portfolio
Read-only

A wallet's Indexfy index holdings with value and profit/loss, plus its Indexfy points.

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": {
      "wallet": "<wallet>"
    },
    "name": "get_wallet_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by enumerating the returned content (holdings value, profit/loss, points), but it says nothing about behavior such as empty portfolios, unsupported wallets, or data freshness. That is adequate-but-thin for a read tool whose annotations already do the heavy lifting.

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?

A single compact sentence with the primary payload (holdings with value and P/L) front-loaded and the secondary payload (points) appended. No filler, though the repeated 'Indexfy' qualifier is slightly redundant.

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?

For a one-parameter read tool with no output schema, the description answers 'what comes back' at a summary level, which is the main thing an agent needs. It is still silent on empty/error results and on whether the response spans multiple indexes, leaving a gap relative to what a portfolio tool typically surfaces.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has one parameter, wallet, with 0% schema description coverage; only a regex pattern constrains it. The description merely repeats the word 'wallet' without clarifying format, chain scope, or whether an address is required versus optional, so it adds essentially no meaning beyond the schema.

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 sentence names a specific resource (a wallet's Indexfy index holdings with value and profit/loss) plus a second returned item (its Indexfy points), so an agent knows exactly what data comes back. It does not name or contrast any sibling (get_index, list_indexes) as alternatives, so the distinction relies on the resource wording alone.

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, when-not-to-use, or alternative named. The agent can infer it is for reading a wallet's portfolio rather than a single index or the index catalog, but that inference is never stated, and nothing says how this differs from get_index.

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