Skip to main content
Glama
Sign In
mcp-server-polymarket

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List combo positions

list_combo_positions
Read-onlyIdempotent

List a wallet's Combo multi-leg positions with each leg, entry cost, current value and status; paginate and sort results to inspect or reconcile holdings.

Instructions

A wallet's Combo (multi-leg) positions with their legs, cost and value.

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": {
      "user": "<user>"
    },
    "name": "list_combo_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesPolymarket wallet (proxy) address.
limitNoRows per page.
cursorNonext_cursor from the previous page. Empty starts at the top.
statusNoEmpty lists what the wallet still holds.
sort_byNo
ascendingNo
condition_idsNoUp to 20 condition ids.

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
itemsNo
has_moreNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world behavior, so the description needn't repeat safety. It adds only output content (legs, cost, value) and says nothing about pagination, default filtering to held positions, or rate limits.

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 short sentence with no wasted words, front-loading the resource and included fields. It is a fragment rather than a complete sentence, but brevity is appropriate for a simple listing tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, paginated positions tool, the description is too thin: it omits when to choose it over related listing tools and does not explain the default 'still holds' scope or sorting options. The output schema covers return fields, but the description still leaves selection and parameter behavior under-specified.

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?

Schema description coverage is 71%, and the description adds no parameter meaning beyond the implicit wallet/user. It ignores limit, cursor, status, sort_by, ascending, and condition_ids, leaving sort behavior and the default status scope under-documented in prose.

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 fragment names a specific resource — a wallet's Combo (multi-leg) positions — and lists the included data: legs, cost and value. That is enough to distinguish it from generic position listing, though it lacks an explicit verb.

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 when-to-use guidance, no mention of alternatives such as list_positions or list_combo_activity, and no prerequisites or exclusions. The agent must infer everything from the name.

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