Get detailed information for a specific prediction market including prices, outcomes, and trading volume.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Market ID or condition_id. If not provided, returns the highest volume active market. | |
| source | No | polymarket or manifold (default: polymarket) | polymarket |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry full weight. It discloses that it returns prices, outcomes, and trading volume, but does not mention read-only status, rate limits, authentication needs, or caching behavior. Adequate but incomplete.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence of 15 words, no unnecessary words, directly communicates purpose and sample output. Ideal conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so description should explain return values. It mentions prices, outcomes, and trading volume but omits structure, format, and the default behavior (if no id, returns highest volume active market). Adequate but with gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema for parameters; it lists output fields but not parameter-specific details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and resource 'detailed information for a specific prediction market', listing example fields (prices, outcomes, trading volume). It distinguishes from sibling tools by implying a specific market rather than browsing or trending, but does not explicitly differentiate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like browse_prediction_markets or get_trending_predictions. The description does not mention use cases, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.