Skip to main content
Glama

waiaas_pm_get_orders

Retrieve Polymarket CLOB orders for a specific wallet, with filtering options by order status (LIVE, MATCHED, CANCELLED) to monitor trading activity.

Instructions

Get Polymarket CLOB orders for a wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoWallet ID. Auto-resolved for single-wallet sessions.
statusNoFilter by order status.

Implementation Reference

  • The tool 'waiaas_pm_get_orders' is registered and implemented within 'packages/mcp/src/tools/polymarket.ts'. The implementation uses the provided 'apiClient' to make a GET request to the Polymarket orders endpoint.
    // pm_get_orders
    server.tool(
      'waiaas_pm_get_orders',
      withWalletPrefix('Get Polymarket CLOB orders for a wallet.', walletContext?.walletName),
      {
        wallet_id: z.string().optional().describe('Wallet ID. Auto-resolved for single-wallet sessions.'),
        status: z.enum(['LIVE', 'MATCHED', 'CANCELLED']).optional().describe('Filter by order status.'),
      },
      async (args) => {
        const walletId = args.wallet_id || 'default';
        const params = new URLSearchParams();
        if (args.status) params.set('status', args.status);
        const qs = params.toString();
        const result = await apiClient.get(`/v1/wallets/${walletId}/polymarket/orders${qs ? '?' + qs : ''}`);
        return toToolResult(result);
      },
    );
Behavior2/5

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

With zero annotations provided, description carries full disclosure burden but fails to state safety profile (read-only), pagination behavior, or return structure. 'Get' implies reading orders, but doesn't confirm non-destructive nature or what happens when wallet has no orders.

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 with no filler words. Appropriately front-loaded. However, extreme brevity is insufficient given lack of annotations and output schema—one additional sentence for behavioral context would improve utility without hurting conciseness.

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?

With no annotations, no output schema, and multiple similar siblings (including position vs. order confusion risk), description is too minimal. Should clarify that orders are pending/filled CLOB entries distinct from positions, and mention that status defaults to returning all (or whatever the default is).

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?

Input schema has 100% description coverage (wallet_id auto-resolution and status filter explained). Description mentions 'for a wallet' implying wallet_id, but adds no syntax, format examples, or constraint details beyond what schema already provides. Baseline 3 appropriate given schema completeness.

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?

Clear verb 'Get' and specific resource 'Polymarket CLOB orders' with scope 'for a wallet'. Distinguishes from Hyperliquid siblings via 'Polymarket' and from generic orders via 'CLOB', but lacks explicit differentiation from sibling 'waiaas_pm_get_positions' which could confuse agents unclear on orders vs. positions distinction.

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?

Provides no guidance on when to use this tool versus waiaas_pm_get_positions (filled holdings) or waiaas_hl_get_open_orders (different exchange). Also omits when to use specific status filters (e.g., 'use LIVE to see active orders').

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