Skip to main content
Glama

AINDEX

Prediction market odds

polymarket_odds
Read-only

Polymarket's open events matching a query (a Fed decision, a recession, an election, a company), each with its markets and their odds in percent.

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": {
      "q": "<q>"
    },
    "name": "polymarket_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by disclosing the response shape (events, each containing markets, with odds in percent) which the absent output schema cannot supply. It does not address limits on how many events return, whether resolved/closed events are excluded from 'open', or empty-result behavior.

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?

A single sentence with the resource front-loaded and the return composition trailing. Every clause earns its place: the query examples and the odds-in-percent unit both carry information an agent needs. No filler or restatement of the tool name.

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 one-parameter lookup with no output schema, the definition covers what the tool takes, what it returns, and in what unit. Remaining gaps (result count, treatment of closed markets, no-match behavior) are modest for a read-only search tool. Nothing required to invoke it correctly is missing.

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 description coverage is 0%, so the description must carry the meaning of q, and it does: the parameter is a free-text topic query, not an ID, slug, or ticker, illustrated with four realistic example topics. Length constraints (2-80 chars) remain documented only in the schema, which is fine. This meaningfully improves on a bare 'q: string'.

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?

States a concrete resource and scope: Polymarket open events matching a query, returned with their markets and odds expressed in percent. The parenthetical query examples (Fed decision, recession, election, company) make the domain unambiguous. It stops short of naming a sibling to contrast with, so differentiation from tools like market_screener or market_overview is left to the reader.

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?

Usage is implied rather than stated: the examples of acceptable query topics signal that this is a natural-language topic lookup against prediction markets. There is no explicit when-to-use/when-not guidance and no mention of any alternative tool for related needs. An agent can infer the use case but gets no routing rules.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources