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

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get wallet approvals

get_wallet_approvals
Read-onlyIdempotent

Check which Polymarket contracts a wallet has approved to move its pUSD and outcome tokens. Identifies missing allowances that cause 'not enough balance / allowance' order failures.

Instructions

Which Polymarket contracts a wallet has approved to move its pUSD and outcome tokens. Missing approvals are why orders fail with 'not enough balance / allowance'.

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

Input Schema

NameRequiredDescriptionDefault
userYesPolymarket wallet (proxy) address.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured fields. The description adds token-type scope (pUSD plus outcome tokens) and the diagnostic framing, but says nothing about freshness of on-chain state, per-contract granularity of the result, or whether unapproved contracts appear. Value beyond annotations is modest.

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?

Two short sentences, with the answer shape stated first and the diagnostic rationale second. Every phrase earns its place and nothing is repeated from the name or schema.

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?

For a single-parameter read with a full schema, all annotations, and an output schema, the description covers what would otherwise be missing: what approvals mean and why an agent would call it. Slight gap remains around state freshness and how multiple approvals are keyed, but the return shape is delegated to the output schema as permitted.

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 coverage is 100% for the single 'user' parameter, complete with a hex-address pattern and the note that it is the Polymarket proxy address. The description adds no parameter-level meaning (e.g. whether an EOA or proxy must be supplied), so the baseline 3 applies.

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 description states precisely what is returned: the Polymarket contracts a wallet has approved for moving pUSD and outcome tokens, including the two token types covered. It lacks an explicit verb ('returns'/'lists') but the resource and scope are unambiguous and no sibling tool covers approvals, so disambiguation is not needed.

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 second sentence gives a concrete invocation trigger: use this when an order is failing with 'not enough balance / allowance'. That is real when-to-use guidance. There are no explicit exclusions or named alternatives, but no sibling plausibly overlaps, so the omission is minor.

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