Skip to main content
Glama

Price history + latest frame for a market across a time window

problee_get_market_chart
Read-onlyIdempotent

Get price history + latest for a market. Window defaults to ALL; supports 1H, 1D, 1W.

Examples: Read the 1D price history for a market

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "problee_get_market_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNo
addressNo
chainIdNo
questionNoInstead of address: a covered question, mirrored or not, by its slug or its Kellian or Polymarket link.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / question
      Added value: +{
      +  "description": "Instead of address: a covered question, mirrored or not, by its slug or its Kellian or Polymarket link.",
      +  "maxLength": 2048,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "address"
      -]
    • removedOutput schema / $defs / AgentMarketChartResponse
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "latest": {
      -      "anyOf": [
      -        {
      -          "$ref": "#/$defs/McpMarketPricePoint"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "meta": {
      -      "additionalProperties": false,
      -      "properties": {
      -        "pointCount": {
      -          "maximum": 9007199254740991,
      -          "minimum": 0,
      -          "type": "integer"
      -        },
      -        "pricingTimestampMs": {
      -          "anyOf": [
      -            {
      -              "maximum": 9007199254740991,
      -              "minimum": 0,
      -              "type": "integer"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "snapshotUpdatedAtMs": {
      -          "anyOf": [
      -            {
      -              "maximum": 9007199254740991,
      -              "minimum": 0,
      -              "type": "integer"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        }
      -      },
      -      "required": [
      -        "pointCount",
      -        "snapshotUpdatedAtMs",
      -        "pricingTimestampMs"
      -      ],
      -      "type": "object"
      -    },
      -    "series": {
      -      "items": {
      -        "$ref": "#/$defs/McpMarketPricePoint"
      -      },
      -      "type": "array"
      -    },
      -    "window": {
      -      "enum": [
      -        "1H",
      -        "1D",
      -        "1W",
      -        "ALL"
      -      ],
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "series",
      -    "latest",
      -    "window",
      -    "meta"
      -  ],
      -  "type": "object"
      -}
    • removedOutput schema / properties / result / $ref
      Removed value: -"#/$defs/AgentMarketChartResponse"
    • addedOutput schema / properties / result / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "latest": {
      +        "anyOf": [
      +          {
      +            "$ref": "#/$defs/McpMarketPricePoint"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "meta": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "pointCount": {
      +            "maximum": 9007199254740991,
      +            "minimum": 0,
      +            "type": "integer"
      +          },
      +          "pricingTimestampMs": {
      +            "anyOf": [
      +              {
      +                "maximum": 9007199254740991,
      +                "minimum": 0,
      +                "type": "integer"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "snapshotUpdatedAtMs": {
      +            "anyOf": [
      +              {
      +                "maximum": 9007199254740991,
      +                "minimum": 0,
      +                "type": "integer"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          }
      +        },
      +        "required": [
      +          "pointCount",
      +          "snapshotUpdatedAtMs",
      +          "pricingTimestampMs"
      +        ],
      +        "type": "object"
      +      },
      +      "series": {
      +        "items": {
      +          "$ref": "#/$defs/McpMarketPricePoint"
      +        },
      +        "type": "array"
      +      },
      +      "window": {
      +        "enum": [
      +          "1H",
      +          "1D",
      +          "1W",
      +          "ALL"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "series",
      +      "latest",
      +      "window",
      +      "meta"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "series": {
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "conditionId": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "label": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "points": {
      +              "items": {
      +                "additionalProperties": false,
      +                "properties": {
      +                  "price": {
      +                    "maximum": 1,
      +                    "minimum": 0,
      +                    "type": "number"
      +                  },
      +                  "timestamp": {
      +                    "maximum": 9007199254740991,
      +                    "minimum": -9007199254740991,
      +                    "type": "integer"
      +                  }
      +                },
      +                "required": [
      +                  "timestamp",
      +                  "price"
      +                ],
      +                "type": "object"
      +              },
      +              "type": "array"
      +            }
      +          },
      +          "required": [
      +            "conditionId",
      +            "label",
      +            "points"
      +          ],
      +          "type": "object"
      +        },
      +        "maxItems": 4,
      +        "type": "array"
      +      },
      +      "window": {
      +        "enum": [
      +          "1H",
      +          "1D",
      +          "1W",
      +          "ALL"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "window",
      +      "series"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds the useful default that the window is ALL when omitted, but says nothing about sampling frequency, number of points returned, or how the 'latest' frame interacts with the history series.

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?

Two compact sentences with the core purpose front-loaded and the default window stated immediately after. The trailing 'Examples:' line is essentially a restatement of the same sentence and does not earn much space.

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?

With an output schema present, return shape need not be described, and the annotations carry the safety profile. However, for a 4-parameter tool with 25% schema coverage, the description leaves the address vs question selection and chainId semantics entirely to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% -- the schema documents 'question' (including the 'Instead of address' note) but leaves address and chainId bare. The description contributes only the default for 'window', and even that adds little since the enum already lists the accepted values; address, chainId, and address/question precedence remain unexplained.

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 and resource -- 'Get price history + latest for a market' -- so the agent knows this returns historical series plus a current snapshot, which separates it from state/depth/holders siblings. It stops short of explicitly naming any sibling, so it is not fully disambiguated.

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?

Usage is only implied: the window options and a one-line example ('Read the 1D price history for a market') show how to call it, but nothing says when to prefer this over problee_get_market_state, problee_get_market_trades or problee_get_market_depth, nor any prerequisites.

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.