Skip to main content
Glama

List prediction markets

list_prediction_markets
Read-only

Prediction markets on Indexfy with live YES/NO prices (= implied probability), money in the market, phase and deadlines.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNowords in the question
sectorNo
statusNoopen = still trading; closed = trading ended

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 safety is covered. The description adds useful domain context: prices are live and equal implied probability, and results carry liquidity, phase and deadlines — this compensates for the absence of an output schema. It says nothing about ordering, pagination behavior, or result volume.

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 compact sentence with no filler, and the most decision-relevant detail (live prices as implied probability) comes early. It is efficient but so terse that it reads as a field list rather than an instruction.

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

Completeness3/5

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

For a 4-parameter read tool with no output schema, the description covers return values reasonably well, which is the main burden. However, it omits pagination/limit defaults, result ordering, and any guidance on combining filters, leaving real gaps for an agent deciding how to call it.

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 coverage is only 50%: search and status carry descriptions while limit and sector rely on enum names alone. The description adds no parameter meaning at all — not the default page size of 20, the 50 cap, or how search matches questions — so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase listing what the response contains (YES/NO prices, implied probability, liquidity, phase, deadlines) rather than stating an operation. Combined with the name, an agent can infer it lists markets, but nothing distinguishes it from the singular get_prediction_market sibling.

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?

No when-to-use, when-not-to-use, or alternative is named. The agent is not told to prefer this for browsing versus get_prediction_market for a single lookup, nor that filters are optional.

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