Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

prediction-odds.market_detail

Read-onlyIdempotent

Ask "what are the prediction market odds" — full: every market title, Yes price, all outcomes, liquidity, close time. | 完整列表:每个市场的标题、所属事件、slug、Yes 概率、全部结果选项与价格、流动性、24h 成交额、结算时间,以及口径说明(隐含概率不是真实概率)。参数 limit 与 q 可选。

[zh] 供应方资产「预测市场赔率与流动性」按次计费 $0.08 USDC(或等值积分)。 入参:limit、q。 [en] Vendor asset "预测市场赔率与流动性". Paid per call: $0.08 USDC (or prepaid credits). Args: limit, q. 付款/支付头在 MCP 请求头里带(X-Payment / X-Payment-Tx / Authorization: Bearer fg_…),不要放进参数。

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": "prediction-odds.market_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuinely useful behavior beyond that: per-call pricing ($0.08 USDC), the requirement that payment headers travel in MCP request headers rather than parameters, and a caveat that implied probability is not real probability. It still says nothing about pagination or rate limits despite the 'full list' scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded English sentence is effective, but the content is then repeated three more times (Chinese field list, then the [zh]/[en] payment blocks), which inflates length without adding information. The payment note is well placed at the end, but overall it is longer than necessary.

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?

With no output schema, the enumeration of returned fields is a real contribution and the payment-header requirement is essential for a paid, metered tool. But the two undocumented parameters leave an agent guessing how to scope requests, which matters for a tool promising an exhaustive market list.

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 description coverage is 0% and the schema documents only bare types for q and limit. The description merely restates that both are optional and never explains what q filters on (keyword? market title? event?) or how limit interacts with the 'full list' promise, 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 does state a specific resource (prediction market odds) and enumerates the full field set (titles, Yes price, outcomes, liquidity, close time), and the word 'full' hints at an exhaustive listing. However, it never explicitly contrasts itself with the sibling prediction-odds.top_markets, so an agent must infer that this is the detail/exhaustive variant.

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 guidance, no exclusions, and no routing to the alternative tool. The only usage-ish statement is that limit and q are optional, which is a schema fact rather than guidance on when to pick this tool over top_markets.

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.