Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get price history

get_price_history
Read-only

Retrieve price changes for every market in a Futuur event over time, returning one series per market for charting or trend analysis; pass the event ID and optional look-back window or point limit.

Instructions

Returns how the prices of every market in an event changed over time, one series per market, for charting or trend analysis. Each point has a UTC time and price_percent, the market's price as a percentage from 0 to 100 (50 means 0.50). Takes an EVENT id, not a market id. Long series are thinned evenly (first and last point kept) to max_points per series; total_points tells you how many existed.

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": {
      "id": "<id>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent id, as returned by get_markets. Not a market id.
max_pointsNoMaximum points returned per market series, 2 to 2000. Default 100.
currency_modeNoWhich price history: "play_money" (default, OOM) or "real_money" (USDC/USDT).play_money
time_intervalNoLook-back window ending now: day (24 hours), week (7 days), month (31 days), year (365 days) or all_time. Defaults to all_time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes far beyond by disclosing the downsampling contract (long series thinned evenly, first and last point kept), the per-series cap, and the total_points field that reveals how many points originally existed. That is exactly the behavioral detail an agent needs to interpret a truncated result.

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?

Three front-loaded sentences with no filler: purpose and scope first, output shape second, then the thinning guarantee. The parenthetical '(50 means 0.50)' resolves the percent ambiguity in a few tokens rather than a sentence.

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?

There is no output schema, so the description carries the return-value burden, and it does: point fields (UTC time, price_percent scale) and total_points are all explained. Nothing an agent needs to call this correctly or interpret the response is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it restates the event-vs-market id distinction at the top level and explains that thinning is even and preserves endpoints, which the max_points schema text does not say. It does not elaborate on time_interval or currency_mode beyond the enum descriptions, keeping it below a 5.

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 description opens with a specific verb+resource: it 'Returns how the prices of every market in an event changed over time, one series per market.' It also draws the critical boundary ('Takes an EVENT id, not a market id'), which separates it from market-level siblings like get_market_details.

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?

It gives concrete usage context ('for charting or trend analysis') and a hard precondition on the id parameter, which is the most likely source of misinvocation. It stops short of naming a sibling alternative for single-market price lookups or stating when not to use it, so it is clear but not fully routed.

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