Skip to main content
Glama

Get prediction market

get_prediction_market
Read-only

One market's live state: prices, phase and what can be done next, deadlines, proposal/dispute. With wallet, also its shares, redeemable USDC and solver stake.

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": {
      "id": "<id>"
    },
    "name": "get_prediction_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesprediction market id
walletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine context beyond that: the wallet parameter conditionally expands the response to include shares, redeemable USDC and solver stake. It does not say what happens when the id does not exist or whether the state is cached/fresh, which matters for a live-state read.

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?

A single dense sentence with the returned data front-loaded and the conditional wallet behavior trailing. Nothing is redundant, though the telegraphic colon-and-list style is slightly clipped rather than plainly readable.

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?

With no output schema, the description usefully enumerates the response fields and the conditional augmentation, which is the main thing an agent needs. The remaining gap is error/empty behavior for a bad or unknown market id, minor for a two-parameter read-only lookup.

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 coverage is only 50% — wallet carries just a regex and no prose. The description compensates by explaining what supplying wallet actually returns (shares, redeemable USDC, solver stake), which is real meaning the schema does not convey. The id parameter's effect is only implied by "One market's live state".

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?

"One market's live state" states the resource and its singularity, which implicitly separates it from list_prediction_markets. It then enumerates the payload (prices, phase, deadlines, proposal/dispute), so an agent knows exactly what this tool answers. It stops short of a 5 because no sibling is named as the alternative.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the name alone that this is the single-market lookup versus the list/quote/build siblings. The only implicit routing signal is the word "One".

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