Skip to main content
Glama

Checking prediction market address PnL

prediction_market_address_pnl
Read-onlyIdempotent

Prediction market PnL breakdown for a Polygon wallet, market by market.

When to use:

  • Wallet-level Polymarket track record with per-market cost and proceeds.

Key fields:

  • Total PnL USD = redemption + unrealized value + sell proceeds − buy cost, for that market only.

  • Net Buy Cost USD is what the wallet paid for shares.

  • Net Sell Proceeds USD is what it received for shares sold before resolution.

  • Redemption Value USD is the payout collected after the market settled.

  • Unrealized Value USD is the marked value of shares still held.

  • Resolved says whether the market has settled.

Pitfalls:

  • Each row covers one market. Sum the rows for a wallet total, or use prediction_market_address_summary for the aggregate.

  • The API gives no ROI or share count here. Do not state them.

  • Blank PnL fields mean unavailable data, not zero.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "prediction_market_address_pnl"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRequest for address-level prediction market PnL.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "description": "Request for address-level prediction market PnL.",
      -    "properties": {
      -      "address": {
      -        "description": "Polygon wallet address to analyze.",
      -        "type": "string"
      -      },
      -      "page": {
      -        "default": 1,
      -        "description": "Page number for paginated results.",
      -        "minimum": 1,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "address"
      -    ],
      -    "type": "object"
      -  }
      -]
    • addedInput schema / properties / request / description
      Added value: +"Request for address-level prediction market PnL."
    • addedInput schema / properties / request / properties
      Added value: +{
      +  "address": {
      +    "description": "Polygon wallet address to analyze.",
      +    "type": "string"
      +  },
      +  "page": {
      +    "default": 1,
      +    "description": "Page number for paginated results.",
      +    "minimum": 1,
      +    "type": "integer"
      +  }
      +}
    • addedInput schema / properties / request / required
      Added value: +[
      +  "address"
      +]
    • addedInput schema / properties / request / type
      Added value: +"object"
  2. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "PredictionMarketAddressPnlRequest": {
      -    "description": "Request for address-level prediction market PnL.",
      -    "properties": {
      -      "address": {
      -        "description": "Polygon wallet address to analyze.",
      -        "type": "string"
      -      },
      -      "page": {
      -        "default": 1,
      -        "description": "Page number for paginated results.",
      -        "minimum": 1,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "address"
      -    ],
      -    "type": "object"
      -  }
      -}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "$ref": "#/$defs/PredictionMarketAddressPnlRequest"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "description": "Request for address-level prediction market PnL.",
      +    "properties": {
      +      "address": {
      +        "description": "Polygon wallet address to analyze.",
      +        "type": "string"
      +      },
      +      "page": {
      +        "default": 1,
      +        "description": "Page number for paginated results.",
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "address"
      +    ],
      +    "type": "object"
      +  }
      +]
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so safety is covered. The description adds real context beyond that: what each computed field means arithmetically, that blank PnL fields mean unavailable rather than zero, and that no ROI or share count is returned. It does not describe pagination behavior or result ordering, which keeps it off a 5.

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?

The leading sentence front-loads purpose and scope, and the bolded section headers make the when-to-use, field glossary, and pitfalls skimmable. The field-by-field glossary is long but each entry defines a computed quantity an agent cannot derive from the name alone, so the length is largely earned rather than padding.

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

Completeness5/5

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

An output schema exists, yet the description still defines the ambiguous derived fields and warns that blanks are not zeros, which is the main correctness risk for this tool. Combined with the aggregate alternative and the explicit prohibition on stating ROI or share count, an agent has everything needed to call it and interpret results correctly.

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?

There is effectively one meaningful parameter (nested address, plus a paging field), and schema coverage is 100%, so the schema already carries the parameter documentation. The description never mentions the address argument or what 'Polygon wallet address' means concretely (e.g. address format, whether non-Polymarket wallets return empty). Baseline 3 is appropriate when the schema does the lifting.

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?

States a specific resource (prediction market PnL), a specific scope (a Polygon wallet, market by market), and a specific source (Polymarket). The per-market granularity is stated immediately, which separates it from the wallet-level aggregate sibling without needing the schema.

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

Usage Guidelines4/5

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

The 'When to use' line gives a concrete scenario (wallet-level Polymarket track record with per-market cost and proceeds), and the Pitfalls section routes the aggregate case to `prediction_market_address_summary` explicitly. What is missing is any converse guidance, such as when to prefer `prediction_market_address_trades` or `prediction_market_position_detail`, but the one alternative that matters for the aggregate is named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources