Skip to main content
Glama

Aevum: verified trading records

Check a Polymarket wallet

check_polymarket_wallet
Read-only

A Polymarket wallet's highlight vs its whole record, from Polymarket's own public data: this week / 30 days / all-time results and ranks, max drawdown, and stats over resolved positions (hit rate, average win vs loss, biggest win and loss, how much of the profit came from the top 3 markets). Use for 'is this Polymarket trader actually good?' or when someone shares a viral Polymarket wallet. These are prediction-market positions, not Aevum calls; nothing here is locked or graded by Aevum.

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

Input Schema

NameRequiredDescriptionDefault
addressYesPolymarket wallet (proxy) address, 0x + 40 hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely useful context by naming the data source (Polymarket's own public data) and clarifying that nothing is locked or graded by Aevum. It stops short of covering failure modes such as an address with no Polymarket activity or an invalid/non-proxy address.

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?

One dense paragraph, front-loaded with what the tool returns and closed with the Aevum-boundary caveat. The parenthetical metric list is efficient rather than padded, though the opening clause 'highlight vs its whole record' is slightly abstract before the concrete list arrives.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly, including the derived metrics. The remaining gap is edge-case behavior for wallets with no activity or addresses that aren't Polymarket proxies.

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?

There is a single parameter with 100% schema description coverage, and the schema already specifies the 0x + 40 hex proxy-address format. The description adds no further parameter meaning (e.g. whether an EOA works vs a proxy), so the baseline of 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?

States a specific verb and resource ('A Polymarket wallet's highlight vs its whole record') and enumerates exactly what comes back: weekly/30-day/all-time results and ranks, max drawdown, hit rate, average win vs loss, biggest win/loss, and top-3 market profit concentration. It also explicitly separates itself from Aevum-native concepts ('not Aevum calls; nothing here is locked or graded by Aevum'), which distinguishes it from siblings like get_record and check_payout_wallet.

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

Usage Guidelines4/5

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

Gives concrete triggering scenarios: 'is this Polymarket trader actually good?' and 'when someone shares a viral Polymarket wallet.' It also implies an exclusion by noting the data is prediction-market positions rather than Aevum calls, though it never names the sibling wallet-checking tool (e.g. check_hyperliquid_wallet) as the alternative for other venues.

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