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

graph-polymarket-mcp

by phon3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get_disputed_markets

Find Polymarket markets where UMA oracle resolutions were disputed, revealing contested outcomes for deeper market analysis.

Instructions

Get Polymarket markets that were disputed during the UMA oracle resolution process. Disputes happen when someone challenges a proposed outcome — these are high-signal events.

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_disputed_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
firstNoNumber of disputed markets to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose operational behaviors such as return format, pagination, or safety characteristics. It only adds conceptual context about disputes, leaving the agent without critical behavioral details.

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 sentences, front-loaded, with no waste. The second sentence provides useful context without redundancy.

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?

The description sufficiently explains the tool's purpose and the meaning of disputed markets. With a single optional parameter documented in the schema, the description is adequate for invocation, though it lacks details about the response structure.

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?

The schema fully documents the 'first' parameter with description, default, and bounds. The description adds no additional parameter semantics, so the baseline 3 is appropriate.

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 clearly states the tool retrieves disputed Polymarket markets with a specific verb and resource. It adds context about what disputes are but does not explicitly differentiate from sibling tools like get_market_resolution.

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

Usage Guidelines3/5

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

The description implies the tool is useful for finding high-signal events, but provides no explicit guidance on when to use it versus alternatives or any exclusions. Usage context is implied rather than stated.

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