Skip to main content
Glama

Checking prediction market address trades

prediction_market_address_trades
Read-onlyIdempotent

Prediction market trade history for a Polygon wallet.

Key fields:

  • Share Size is quantity traded in the displayed outcome side.

  • Value USD applies to that row only, not the whole transaction.

Pitfalls:

  • Use this for wallet trade activity, not profitability.

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_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRequest for address-level prediction market trades.

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 trades.",
      -    "properties": {
      -      "address": {
      -        "description": "Polygon wallet address to analyze.",
      -        "type": "string"
      -      },
      -      "dateRange": {
      -        "anyOf": [
      -          {
      -            "description": "Date range via tokens or dates.\nTokens: NOW, ALL_TIME, XMIN_AGO, XD_AGO, XH_AGO, XY_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nDurations are exact rolling UTC timestamps at both ends: 1D_AGO equals 24H_AGO; 1Y_AGO equals 365 days. Bare duration aliases and case variants are supported.\nExplicit dates and calendar tokens keep calendar boundaries and inclusive final dates. TODAY_START is current-day midnight. Date-only endpoints keep their calendar contracts.\nALL_TIME is full history. It resolves to 2009-01-03. Use ALL_TIME instead of a very large day count.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
      -            "properties": {
      -              "from": {
      -                "description": "Start token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps; dates and calendar tokens start at midnight.",
      -                "type": "string"
      -              },
      -              "to": {
      -                "description": "End token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps without an extra day. Dates and calendar tokens include the final date; TODAY_START stays at midnight.",
      -                "type": "string"
      -              }
      -            },
      -            "required": [
      -              "from",
      -              "to"
      -            ],
      -            "type": "object"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional date range for address trades. Defaults to the last 30 days."
      -      },
      -      "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 trades."
    • addedInput schema / properties / request / properties
      Added value: +{
      +  "address": {
      +    "description": "Polygon wallet address to analyze.",
      +    "type": "string"
      +  },
      +  "dateRange": {
      +    "anyOf": [
      +      {
      +        "additionalProperties": false,
      +        "description": "Date range via tokens or dates.\nTokens: NOW, ALL_TIME, XMIN_AGO, XD_AGO, XH_AGO, XY_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nDurations are exact rolling UTC timestamps at both ends: 1D_AGO equals 24H_AGO; 1Y_AGO equals 365 days. Bare duration aliases and case variants are supported.\nExplicit dates and calendar tokens keep calendar boundaries and inclusive final dates. TODAY_START is current-day midnight. Date-only endpoints keep their calendar contracts.\nALL_TIME is full history. It resolves to 2009-01-03. Use ALL_TIME instead of a very large day count.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
      +        "properties": {
      +          "from": {
      +            "description": "Start token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps; dates and calendar tokens start at midnight.",
      +            "type": "string"
      +          },
      +          "to": {
      +            "description": "End token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps without an extra day. Dates and calendar tokens include the final date; TODAY_START stays at midnight.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "from",
      +          "to"
      +        ],
      +        "type": "object"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ],
      +    "default": null,
      +    "description": "Optional date range for address trades. Defaults to the last 30 days."
      +  },
      +  "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. Changed1 schema field changed
    • changedInput schema / properties / request / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "description": "Request for address-level prediction market trades.",
      -    "properties": {
      -      "address": {
      -        "description": "Polygon wallet address to analyze.",
      -        "type": "string"
      -      },
      -      "dateRange": {
      -        "anyOf": [
      -          {
      -            "description": "Date range via tokens or dates.\nTokens: NOW, ALL_TIME, XMIN_AGO, XD_AGO, XH_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nALL_TIME is full history. It resolves to 2009-01-03. Use ALL_TIME instead of a very large day count.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
      -            "properties": {
      -              "from": {
      -                "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      -                "type": "string"
      -              },
      -              "to": {
      -                "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      -                "type": "string"
      -              }
      -            },
      -            "required": [
      -              "from",
      -              "to"
      -            ],
      -            "type": "object"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional date range for address trades. Defaults to the last 30 days."
      -      },
      -      "page": {
      -        "default": 1,
      -        "description": "Page number for paginated results.",
      -        "minimum": 1,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "address"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "description": "Request for address-level prediction market trades.",
      +    "properties": {
      +      "address": {
      +        "description": "Polygon wallet address to analyze.",
      +        "type": "string"
      +      },
      +      "dateRange": {
      +        "anyOf": [
      +          {
      +            "description": "Date range via tokens or dates.\nTokens: NOW, ALL_TIME, XMIN_AGO, XD_AGO, XH_AGO, XY_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nDurations are exact rolling UTC timestamps at both ends: 1D_AGO equals 24H_AGO; 1Y_AGO equals 365 days. Bare duration aliases and case variants are supported.\nExplicit dates and calendar tokens keep calendar boundaries and inclusive final dates. TODAY_START is current-day midnight. Date-only endpoints keep their calendar contracts.\nALL_TIME is full history. It resolves to 2009-01-03. Use ALL_TIME instead of a very large day count.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
      +            "properties": {
      +              "from": {
      +                "description": "Start token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps; dates and calendar tokens start at midnight.",
      +                "type": "string"
      +              },
      +              "to": {
      +                "description": "End token or date (YYYY-MM-DD or ___-MM-DD). Durations use exact rolling UTC timestamps without an extra day. Dates and calendar tokens include the final date; TODAY_START stays at midnight.",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "from",
      +              "to"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "Optional date range for address trades. Defaults to the last 30 days."
      +      },
      +      "page": {
      +        "default": 1,
      +        "description": "Page number for paginated results.",
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "address"
      +    ],
      +    "type": "object"
      +  }
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / request / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "description": "Request for address-level prediction market trades.",
      -    "properties": {
      -      "address": {
      -        "description": "Polygon wallet address to analyze.",
      -        "type": "string"
      -      },
      -      "dateRange": {
      -        "anyOf": [
      -          {
      -            "description": "Date range via tokens or dates.\nTokens: NOW, XMIN_AGO, XD_AGO, XH_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
      -            "properties": {
      -              "from": {
      -                "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      -                "type": "string"
      -              },
      -              "to": {
      -                "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      -                "type": "string"
      -              }
      -            },
      -            "required": [
      -              "from",
      -              "to"
      -            ],
      -            "type": "object"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional date range for address trades. Defaults to the last 30 days."
      -      },
      -      "page": {
      -        "default": 1,
      -        "description": "Page number for paginated results.",
      -        "minimum": 1,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "address"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "description": "Request for address-level prediction market trades.",
      +    "properties": {
      +      "address": {
      +        "description": "Polygon wallet address to analyze.",
      +        "type": "string"
      +      },
      +      "dateRange": {
      +        "anyOf": [
      +          {
      +            "description": "Date range via tokens or dates.\nTokens: NOW, ALL_TIME, XMIN_AGO, XD_AGO, XH_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nALL_TIME is full history. It resolves to 2009-01-03. Use ALL_TIME instead of a very large day count.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
      +            "properties": {
      +              "from": {
      +                "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      +                "type": "string"
      +              },
      +              "to": {
      +                "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "from",
      +              "to"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "Optional date range for address trades. Defaults to the last 30 days."
      +      },
      +      "page": {
      +        "default": 1,
      +        "description": "Page number for paginated results.",
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "address"
      +    ],
      +    "type": "object"
      +  }
      +]
  4. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "DateRange": {
      -    "description": "Date range via tokens or dates.\nTokens: NOW, XMIN_AGO, XD_AGO, XH_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
      -    "properties": {
      -      "from": {
      -        "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      -        "type": "string"
      -      },
      -      "to": {
      -        "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "from",
      -      "to"
      -    ],
      -    "type": "object"
      -  },
      -  "PredictionMarketAddressTradesRequest": {
      -    "description": "Request for address-level prediction market trades.",
      -    "properties": {
      -      "address": {
      -        "description": "Polygon wallet address to analyze.",
      -        "type": "string"
      -      },
      -      "dateRange": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/$defs/DateRange"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "description": "Optional date range for address trades. Defaults to the last 30 days."
      -      },
      -      "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/PredictionMarketAddressTradesRequest"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "description": "Request for address-level prediction market trades.",
      +    "properties": {
      +      "address": {
      +        "description": "Polygon wallet address to analyze.",
      +        "type": "string"
      +      },
      +      "dateRange": {
      +        "anyOf": [
      +          {
      +            "description": "Date range via tokens or dates.\nTokens: NOW, XMIN_AGO, XD_AGO, XH_AGO; THIS_YEAR_START, THIS_QUARTER_START, THIS_MONTH_START, THIS_WEEK_START, TODAY_START; LAST_WEEK_START/END, LAST_MONTH_START/END, LAST_QUARTER_START/END, LAST_YEAR_START/END.\nWeek starts Monday. Quarters are calendar. Dates: YYYY-MM-DD or ___-MM-DD (year omitted).\nPlease check detailed system instructions for more information.",
      +            "properties": {
      +              "from": {
      +                "description": "Start value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      +                "type": "string"
      +              },
      +              "to": {
      +                "description": "End value: token (see above) or date (YYYY-MM-DD or ___-MM-DD).",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "from",
      +              "to"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "Optional date range for address trades. Defaults to the last 30 days."
      +      },
      +      "page": {
      +        "default": 1,
      +        "description": "Page number for paginated results.",
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "address"
      +    ],
      +    "type": "object"
      +  }
      +]
  5. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds interpretation guidance for the output values (Share Size is per outcome side; Value USD is per row, not per transaction), which is genuinely useful, but it says nothing about pagination depth, rate limits, or coverage of chains beyond Polygon.

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?

Front-loaded one-line purpose, then two compact labeled sections. Every bullet carries non-obvious information; there is no filler or restatement of the name.

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?

For a single-request-parameter read tool with an output schema and full schema coverage, the description supplies the missing piece — how to read Share Size and Value USD. Minor gap: no mention of result limits or ordering for the paginated trade list.

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%, so the address, page, and dateRange parameters (including the 30-day default and token syntax) are fully documented in the schema. The description adds no parameter-level meaning beyond that, which matches the baseline of 3.

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?

States a specific verb+resource: trade history for a Polygon wallet, restricted to prediction markets. It also implicitly separates itself from profitability tooling ("not profitability"), though it does not name the sibling (e.g. prediction_market_address_pnl) directly.

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 Pitfalls line gives an explicit exclusion — "Use this for wallet trade activity, not profitability" — which is real routing guidance. It lacks a positive recommendation of which tool to use instead and gives no prerequisites or context about when a wallet has no history.

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