Skip to main content
Glama

waiaas_pm_get_positions

Retrieve Polymarket prediction market positions for a wallet to track investments and analyze market exposure.

Instructions

Get Polymarket prediction market positions for a wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoWallet ID. Auto-resolved for single-wallet sessions.

Implementation Reference

  • The handler for 'waiaas_pm_get_positions' is implemented using server.tool within the registerPolymarketTools function. It fetches positions from the API.
    // pm_get_positions
    server.tool(
      'waiaas_pm_get_positions',
      withWalletPrefix('Get Polymarket prediction market positions for a wallet.', walletContext?.walletName),
      {
        wallet_id: z.string().optional().describe('Wallet ID. Auto-resolved for single-wallet sessions.'),
      },
      async (args) => {
        const walletId = args.wallet_id || 'default';
        const result = await apiClient.get(`/v1/wallets/${walletId}/polymarket/positions`);
        return toToolResult(result);
      },
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Get' implies a safe read-only operation, but the description lacks details on data source (on-chain vs Polymarket API), rate limits, or return behavior when no positions exist.

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?

Single sentence with zero waste. Information density is optimal with specific domain (Polymarket), resource type (positions), and target (wallet) all front-loaded.

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

Completeness4/5

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

Given low complexity (1 optional param) and 100% input schema coverage, the description is adequate for tool selection. It lacks return value documentation (no output schema), but the 'get positions' pattern is sufficiently standard that the naming carries the semantic load.

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% (wallet_id is fully documented with auto-resolution note). The description adds no explicit parameter guidance, but with complete schema coverage, the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'Get' with clear resource 'Polymarket prediction market positions'. The inclusion of 'Polymarket' effectively distinguishes this from sibling tools like waiaas_hl_get_positions (Hyperliquid) and waiaas_pm_get_orders/orders/balance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance is provided. While the specificity of 'Polymarket positions' implies usage context, there is no mention of when to prefer this over waiaas_pm_get_orders or waiaas_pm_get_balance.

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