Skip to main content
Glama
Sign In
HeadlessTracker

HeadlessTracker

by tamasPetki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_polymarket_positions

Retrieve your Polymarket prediction-market positions grouped by event, showing market title, outcome, quantity, current price, value, cost, PnL, redeemable status, and end date.

Instructions

Returns Polymarket prediction-market positions, grouped by event when possible. Use this when the user asks about their Polymarket bets specifically: 'show my Polymarket positions', 'how am I doing on Polymarket', 'what bets do I have', 'show my prediction market positions', 'election bets', 'sports bets', etc. For general portfolio queries that mention Polymarket alongside crypto/stocks, prefer get_holdings (with optional asset_class='prediction' filter). Each position includes: - market title (human-readable question, e.g. 'Will X win the 2024 election?') - outcome ('Yes' / 'No' / specific candidate name) - quantity (conditional tokens held, each worth 0-1 USDC) - currentPrice (0-1, market's current implied probability) - currentValue (USD), avgCost (USD per token), cashPnl (realized + unrealized) - redeemable (true if market resolved and you can claim payout) - mergeable (true if you can merge Yes+No tokens for guaranteed USDC) - endDate (when the market resolves) Inputs (optional): - account_id: scope to one Polymarket account (if you have multiple). - group_by_event: 'true' (default) groups Yes+No outcomes for the same market; 'false' returns one row per asset. - resolved_only: 'true' returns only redeemable positions (markets that have resolved). Default 'false' returns everything. Returns position data only. Not financial advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_polymarket_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoScope to one Polymarket account if several are configured. Omit for all.
group_by_eventNoDefault true: groups Yes+No outcomes of the same market into one event row. Set false for one row per asset/outcome.
resolved_onlyNoDefault false (return all positions). Set true to return only redeemable positions in markets that have already resolved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.12

TDQS

A4.6/5.0
Behavior4/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 of transparency. It details the output fields (market title, outcome, quantity, currentPrice, etc.), explains defaults for optional parameters, and includes a disclaimer ('Not financial advice'). It does not mention authentication or rate limits, but the behavioral description is thorough and consistent.

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 well-structured: purpose statement first, then usage guidance, then output field details, then parameter descriptions. Every sentence adds necessary information; there is no redundancy. It is appropriately sized and front-loaded with the key purpose.

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?

Despite lacking an output schema, the description compensates by thoroughly enumerating the returned fields. It covers inputs and outputs adequately for an AI agent to understand the tool's behavior. Minor omissions (e.g., error handling, rate limits) prevent a perfect score.

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

Parameters4/5

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

Schema coverage is 100%, so each parameter already has a description. The description adds extra value by explaining defaults (group_by_event defaults true, resolved_only defaults false) and provides context on when to use each parameter. This goes beyond the schema alone.

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 that the tool returns Polymarket prediction-market positions grouped by event. It provides specific example queries and distinguishes itself from the sibling tool get_holdings, which is intended for general portfolio queries. The verb 'returns' and resource 'Polymarket positions' are precise.

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool ('when the user asks about their Polymarket bets') with concrete examples, and when not to use it ('for general portfolio queries...prefer get_holdings'). It also suggests an alternative filter for get_holdings. This is exemplary guidance.

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

Deploy Server

Other Tools