graph-polymarket-mcp

get_trader_usdc_flows

Show USDC deposit and withdrawal history for a Polymarket trader. See inbound and outbound transfers to track when they fund or withdraw.

Instructions

Get USDC deposit/withdrawal history for a trader. Shows inbound and outbound USDC transfers, useful for tracking when traders fund or withdraw from Polymarket.

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

Input Schema

Name	Required	Description	Default
`first`	No	Number of transfers to return
`address`	Yes	Ethereum address of the trader
`direction`	No	Filter by transfer direction	both

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0May 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool 'Shows inbound and outbound USDC transfers,' which is useful, but it does not disclose return format, pagination behavior, or whether only confirmed transfers are included. This adds some context but leaves important behavioral traits unaddressed.

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?

The description is two sentences, front-loaded with the primary action, and contains zero fluff. Every word contributes to understanding the tool's purpose and use case.

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 should explain what is returned. It gives a high-level view ('Shows inbound and outbound USDC transfers') but does not describe the individual fields (e.g., amount, timestamp, transaction hash) or any default time range. This is a moderate gap for a tool with no output schema.

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% (all three parameters have descriptions), so the baseline is 3. The description's mention of 'deposit/withdrawal' and 'inbound/outbound' loosely aligns with the direction parameter but does not add any semantic detail beyond what the schema already specifies.

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 clearly states 'Get USDC deposit/withdrawal history for a trader' with a specific verb and resource. It distinguishes itself from sibling tools like get_trader_profile and get_user_positions by focusing on USDC flows, making the tool's purpose immediately identifiable.

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?

The description provides clear context with 'useful for tracking when traders fund or withdraw from Polymarket.' However, it does not explicitly name alternative tools or mention when not to use this tool, so it lacks the explicit exclusions that would earn a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.