Skip to main content
Glama

waiaas_pm_get_markets

Retrieve Polymarket prediction markets with category, status, keyword, or limit filters to analyze crypto market insights.

Instructions

Browse Polymarket prediction markets with optional filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoMarket category filter.
statusNoMarket status filter (e.g., active, resolved).
keywordNoSearch keyword.
limitNoMaximum number of markets to return.

Implementation Reference

  • Implementation of the 'waiaas_pm_get_markets' tool in the Polymarket MCP tool set. It handles the registration, input schema, and executes an API call to the polymarket service.
    // pm_get_markets
    server.tool(
      'waiaas_pm_get_markets',
      'Browse Polymarket prediction markets with optional filters.',
      {
        category: z.string().optional().describe('Market category filter.'),
        status: z.string().optional().describe('Market status filter (e.g., active, resolved).'),
        keyword: z.string().optional().describe('Search keyword.'),
        limit: z.string().optional().describe('Maximum number of markets to return.'),
      },
      async (args) => {
        const params = new URLSearchParams();
        if (args.category) params.set('category', args.category);
        if (args.status) params.set('status', args.status);
        if (args.keyword) params.set('keyword', args.keyword);
        if (args.limit) params.set('limit', args.limit);
        const qs = params.toString();
        const result = await apiClient.get(`/v1/polymarket/markets${qs ? '?' + qs : ''}`);
        return toToolResult(result);
      },
    );
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. States 'browse' implying read-only, but doesn't confirm safety, disclose pagination behavior (despite 'limit' param), mention rate limits, or describe what data structure is returned. Lacks critical behavioral context for a data retrieval tool.

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?

Single sentence of 7 words that leads with the verb. No wasted words or redundancy. However, given the lack of annotations and output schema, the extreme brevity may be insufficient rather than optimally concise.

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

Completeness2/5

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

For a 4-parameter tool with no annotations, no output schema, and closely named siblings (get_market_detail), the description is incomplete. Missing: indication this returns multiple items, how results are ordered, or what distinguishes this from the 'detail' endpoint.

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 description coverage is 100%, so the schema adequately documents each parameter (category, status, keyword, limit). The description adds only that these are 'optional filters,' which marginally reinforces their purpose but adds no syntax, format, or example guidance beyond the schema.

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 clearly identifies the resource (Polymarket prediction markets) and action (browse), distinguishing it from Hyperliquid siblings (waiaas_hl_get_markets). However, it doesn't explicitly distinguish from waiaas_pm_get_market_detail (singular), leaving ambiguity about whether this returns a list or single item.

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?

Mentions 'optional filters' which loosely implies all parameters are optional, but provides no explicit guidance on when to use this vs. waiaas_pm_get_market_detail or waiaas_pm_get_events. No prerequisites or conditions are stated.

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