Skip to main content
Glama

Summarizing prediction market address

prediction_market_address_summary
Read-onlyIdempotent

Prediction market summary metrics for a Polygon wallet.

When to use:

  • First wallet-level Polymarket tool for a quick trader overview.

  • Use before detailed address trades/PnL when the user asks for a general wallet profile, activity summary, or whether a wallet is active on Polymarket.

Key fields:

  • Markets Traded and Markets Won are lifetime counts; Win Rate is won / traded.

  • Total PnL USD = realized + unrealized.

  • First Seen and Wallet Age (Days) show how long the wallet has been active on Polymarket.

Pitfalls:

  • The API gives no trade count, volume, or ROI here. Do not state them. For per-market cost and proceeds use prediction_market_address_pnl.

  • 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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRequest for address-level prediction market summary metrics.

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 summary metrics.",
      -    "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 summary metrics."
    • 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: -{
      -  "PredictionMarketAddressSummaryRequest": {
      -    "description": "Request for address-level prediction market summary metrics.",
      -    "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/PredictionMarketAddressSummaryRequest"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "description": "Request for address-level prediction market summary metrics.",
      +    "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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the data semantics: lifetime counts, Win Rate formula, Total PnL = realized + unrealized, and blank fields meaning unavailable rather than zero. Those are genuinely useful disclosures beyond the annotations. It stops short of describing pagination behavior or response shape, but the output schema covers returns.

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?

Front-loaded purpose followed by clearly labeled When-to-use, Key fields, and Pitfalls sections, so scanning is easy. Slightly over-built for a single-parameter tool, and the field explanations partly overlap the output schema, but the pitfall guidance is not wasted text.

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?

For a simple one-parameter summary tool with full schema coverage and an output schema, nothing material is missing: triggers, sibling routing, field interpretation, and explicit warnings about absent metrics are all present. An agent can call it and interpret the result without further context.

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 parameter object with an address and an unmentioned page field, and schema description coverage is 100%, so the schema already carries the semantics. The description confirms the address is a Polygon wallet but adds no format, validation, or paging guidance, which matches the baseline-3 expectation when the schema does the work.

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 opening line names a specific resource and scope: prediction market summary metrics for a Polygon wallet. The 'When to use' section explicitly positions it as the first wallet-level Polymarket tool versus detailed alternatives, so an agent can distinguish it from prediction_market_address_pnl and prediction_market_address_trades without opening any schema.

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

Usage Guidelines5/5

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

It states explicit trigger conditions (general wallet profile, activity summary, is-this-wallet-active) and names the alternative for per-market cost/proceeds. The sequencing advice ('use before detailed address trades/PnL') gives a concrete ordering rule rather than vague context.

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