Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

waiaas_pm_get_pnl

Retrieve Polymarket profit and loss summary for a wallet to track trading performance and financial outcomes.

Instructions

Get Polymarket profit and loss summary for a wallet.

Input Schema

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

Implementation Reference

  • packages/mcp/src/tools/polymarket.ts:117-129 (handler)
    The handler for 'waiaas_pm_get_pnl' which fetches PnL data from the API.
    // pm_get_pnl
server.tool(
  'waiaas_pm_get_pnl',
  withWalletPrefix('Get Polymarket profit and loss summary 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/pnl`);
    return toToolResult(result);
  },
);

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It lacks safety confirmations (read-only vs write), data freshness indicators, or disclosure of what the 'summary' includes (e.g., time period, fees, realized PnL). Mentions 'Polymarket' indicating external data source, but insufficient for a financial data tool.

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?

Extremely concise at 9 words. Single sentence front-loads the action and domain. No redundancy or filler.

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?

Adequate for a single-parameter read operation with fully documented schema. However, given the absence of an output schema and the complexity of PnL calculations, the description omits return value expectations that would assist agent interpretation.

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%, establishing baseline 3. The description omits parameter discussion entirely, relying on the schema's 'wallet_id' description. No additional semantic value added (e.g., format examples, behavior when omitted in multi-wallet sessions).

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), specific resource (Polymarket profit and loss summary), and scope (wallet). It distinguishes from generic balance tools by specifying PnL and from Hyperliquid tools via the 'Polymarket' reference. Falls short of 5 by not explicitly differentiating from sibling waiaas_pm_get_positions or defining the PnL methodology (realized vs unrealized).

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 waiaas_pm_get_positions, waiaas_pm_get_balance, or waiaas_get_defi_positions. Does not mention if this is for closed positions, open positions, or both.

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