Skip to main content
Glama

Wallet overview

wallet_overview
Read-onlyIdempotent

Summarize one wallet's trading profile and performance.

Wallet profit tracking for any Polymarket address: lifetime P&L
(Polymarket's figure), market_win_rate over resolved markets, a net
profit factor, indexed volume and activity, category mix and leaderboard
rankings. Accepts a 0x wallet address or an OrcaLayer nickname. Returns a
compact summary rather than the full raw record, so it stays readable for
heavy wallets. A `notes` block defines each field; market_win_rate has
the same basis and value as in the leaderboard tool.

While the wallet's stats are still being computed server-side, the result
is a ``{"status": "computing", "retry_after_seconds": N}`` notice instead of
data; N is the number of seconds after which the stats are expected to be
ready.

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_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x wallet address (proxy or signer) or OrcaLayer nickname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / address / description
      Added value: +"0x wallet address (proxy or signer) or OrcaLayer nickname."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world reads, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: results are a compact summary rather than the raw record, a notes block defines each field, and a pending-computation state returns {"status": "computing", "retry_after_seconds": N} — an agent must handle that retry loop. It stops short of stating auth requirements or error behavior for malformed addresses.

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?

The lead sentence is front-loaded and the field enumeration is informative rather than padding. The two-part opening ('Summarize...' followed by 'Wallet profit tracking for any Polymarket address:') is mildly redundant, but nothing is wasted across the rest of the text.

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?

There is no output schema, so the description must carry return-shape burden, and it does: field list, the notes block, the compact-summary caveat for heavy wallets, and the computing-state payload. Only marginal gaps remain, such as invalid-address or rate-limit behavior for an open-world read.

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?

With a single parameter at 100% schema description coverage, the schema already explains that the address may be a 0x wallet (proxy or signer) or an OrcaLayer nickname. The description repeats that same fact without adding format rules, validation constraints, or normalization behavior, so the baseline 3 applies.

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 opens with a specific verb and scope ('Summarize one wallet's trading profile and performance') and then enumerates the exact dimensions returned (lifetime P&L, market_win_rate, profit factor, volume, category mix, leaderboard rank). An agent knows precisely what resource this acts on and what it produces.

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?

Usage is implied by the scope ('one wallet') and by the note that market_win_rate shares a basis with the leaderboard tool, which hints at an alternative for ranking views. However, there is no explicit when-to-use / when-not statement, and the distinction from wallet_positions or leaderboard is left to inference.

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.