Skip to main content
Glama

waiaas_pm_get_market_detail

Retrieve detailed information about a specific Polymarket prediction market using its condition ID to analyze market data and outcomes.

Instructions

Get detailed information about a specific Polymarket prediction market.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
condition_idYesMarket condition ID.

Implementation Reference

  • The implementation of the 'waiaas_pm_get_market_detail' MCP tool handler within the Polymarket tools registration. It takes 'condition_id' as an argument and performs a GET request to the Polymarket API.
    // pm_get_market_detail
    server.tool(
      'waiaas_pm_get_market_detail',
      'Get detailed information about a specific Polymarket prediction market.',
      {
        condition_id: z.string().describe('Market condition ID.'),
      },
      async (args) => {
        const result = await apiClient.get(`/v1/polymarket/markets/${args.condition_id}`);
        return toToolResult(result);
      },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden. While 'Get' implies read-only behavior, the description lacks details on error handling (what happens if condition_id is invalid), data freshness, or what specific 'detailed information' is returned.

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, efficient sentence of 10 words. Front-loaded with the action verb and wastes no words. Every element earns its place.

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 simple single-parameter read tool with full schema coverage, the description is minimally viable. However, given siblings with similar scopes exist (get_events, get_markets), additional context on what constitutes 'detailed information' would improve selection accuracy.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema fully documents the 'condition_id' parameter. The description adds domain context by specifying this is for 'Polymarket', but doesn't add syntax details or value constraints beyond what the schema provides. Baseline 3 is appropriate.

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?

The description uses a specific verb ('Get') and clearly identifies the resource ('Polymarket prediction market'). The word 'specific' implies a distinction from the sibling tool 'waiaas_pm_get_markets' (likely a list operation), though it doesn't explicitly name 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?

No guidance provided on when to use this versus sibling tools like 'waiaas_pm_get_markets' or 'waiaas_pm_get_events'. No mention of prerequisites like needing a valid condition_id from a previous list call.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minhoyoo-iotrust/WAIaaS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server