Skip to main content
Glama

Market history

market_history
Read-onlyIdempotent

Daily history: funding rate, open interest, price and liquidation totals for one pair (archived since 2026-03-18), or daily whale buy/sell flow for one coin (since 2026-06-18). The free plans cover the last day; a paid plan reaches the full archive. Descriptive market data only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoRead the daily whale buy and sell flow lane for one coin instead, for example BTC, recorded since 2026-06-18. Passing coin selects that lane and pair is then ignored. This is the one tool here where coin and pair are different questions, not two spellings of one.
daysNoHow many recorded days to return. Defaults to the whole window, which is also the ceiling: 1 on the free plans and 400 on Pro (Starter sits between). Asking for more returns the cap, and the payload says so in `capped`. Both lanes settle several days behind live by design, so read as_of and data_age_days before calling any of it current.
pairNoRead the daily market lane for one pair: funding, open interest, price and liquidation totals, recorded since 2026-03-18. For example ETH/USD; a bare symbol like ETH is read as ETH/USD, and BTC/USD is the default. Ignored when coin is passed, because coin selects the other lane.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoThe coin, when the daily whale-flow lane was read.
pairNoThe pair, when the daily market lane was read.
as_ofNoThe newest day in this reply. Not today: both lanes settle several days behind live by design.
priceNoDaily price readings.
staleNoTrue only when the lane is further back than its own settle horizon explains.
cappedNoPresent only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit.
fundingNoDaily funding readings, oldest first, each carrying its own coverage evidence.
availableNoFalse when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess.
depth_noteNoHow far back the data behind this answer reaches.
stale_noteNoPresent when stale is true: how far past the horizon it has fallen.
access_noteNoWhat this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears.
liquidationsNoDaily forced-close totals.
coverage_noteNoPresent when stale is false: why the newest day is not today, and that these days must not be described as current.
data_age_daysNoHow many days back as_of sits.
days_returnedNoHow many recorded days came back.
open_interestNoDaily open interest readings.
hour_of_day_utcNoWhat a typical hour looks like for this coin, as medians per UTC hour. Absent under 14 recorded days.
whale_flow_dailyNoDaily whale buy and sell dollars, when the coin lane was read.
expected_lag_daysNoHow far behind live this lane is meant to run, so a healthy lag can be told from a stopped one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / days / description
      Previous value: -"How many recorded days to return. Defaults to the whole window, which is also the ceiling: 1 on the free plans and 400 on a paid plan. Asking for more returns the cap, and the payload says so in `capped`. Both lanes settle several days behind live by design, so read as_of and data_age_days before calling any of it current."New value: +"How many recorded days to return. Defaults to the whole window, which is also the ceiling: 1 on the free plans and 400 on Pro (Starter sits between). Asking for more returns the cap, and the payload says so in `capped`. Both lanes settle several days behind live by design, so read as_of and data_age_days before calling any of it current."
  2. Changed1 schema field changed
    • changedInput schema / properties / days / description
      Previous value: -"How many recorded days to return. Defaults to the whole window, which is also the ceiling: 30 keyless and 400 on a paid plan. Asking for more returns the cap, and the payload says so in `capped`. Both lanes settle several days behind live by design, so read as_of and data_age_days before calling any of it current."New value: +"How many recorded days to return. Defaults to the whole window, which is also the ceiling: 1 on the free plans and 400 on a paid plan. Asking for more returns the cap, and the payload says so in `capped`. Both lanes settle several days behind live by design, so read as_of and data_age_days before calling any of it current."
  3. Changed1 schema field changed
    • changedInput schema / properties / days / description
      Previous value: -"How many recorded days to return. Defaults to the whole window, which is also the ceiling: 30 keyless and 400 on a developer plan. Asking for more returns the cap, and the payload says so in `capped`. Both lanes settle several days behind live by design, so read as_of and data_age_days before calling any of it current."New value: +"How many recorded days to return. Defaults to the whole window, which is also the ceiling: 30 keyless and 400 on a paid plan. Asking for more returns the cap, and the payload says so in `capped`. Both lanes settle several days behind live by design, so read as_of and data_age_days before calling any of it current."
  4. Changed4 schema fields changed
    • addedInput schema / properties / coin / description
      Added value: +"Read the daily whale buy and sell flow lane for one coin instead, for example BTC, recorded since 2026-06-18. Passing coin selects that lane and pair is then ignored. This is the one tool here where coin and pair are different questions, not two spellings of one."
    • addedInput schema / properties / days / description
      Added value: +"How many recorded days to return. Defaults to the whole window, which is also the ceiling: 30 keyless and 400 on a developer plan. Asking for more returns the cap, and the payload says so in `capped`. Both lanes settle several days behind live by design, so read as_of and data_age_days before calling any of it current."
    • addedInput schema / properties / pair / description
      Added value: +"Read the daily market lane for one pair: funding, open interest, price and liquidation totals, recorded since 2026-03-18. For example ETH/USD; a bare symbol like ETH is read as ETH/USD, and BTC/USD is the default. Ignored when coin is passed, because coin selects the other lane."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "access_note": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears."
      +    },
      +    "as_of": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The newest day in this reply. Not today: both lanes settle several days behind live by design."
      +    },
      +    "available": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess."
      +    },
      +    "capped": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "applied": {
      +              "description": "The value actually used.",
      +              "type": "number"
      +            },
      +            "argument": {
      +              "description": "Which argument was cut down, for example limit or hours.",
      +              "type": "string"
      +            },
      +            "by": {
      +              "description": "Why it was cut: keyless for the free ceiling, plan_max for a paid ceiling, tool_max for a ceiling no plan raises.",
      +              "type": "string"
      +            },
      +            "max": {
      +              "description": "The ceiling that applied.",
      +              "type": "number"
      +            },
      +            "requested": {
      +              "description": "The value the caller asked for.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "argument",
      +            "requested",
      +            "applied",
      +            "max",
      +            "by"
      +          ],
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit."
      +    },
      +    "coin": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The coin, when the daily whale-flow lane was read."
      +    },
      +    "coverage_note": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Present when stale is false: why the newest day is not today, and that these days must not be described as current."
      +    },
      +    "data_age_days": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "How many days back as_of sits."
      +    },
      +    "days_returned": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "How many recorded days came back."
      +    },
      +    "depth_note": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "How far back the data behind this answer reaches."
      +    },
      +    "expected_lag_days": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "How far behind live this lane is meant to run, so a healthy lag can be told from a stopped one."
      +    },
      +    "funding": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Daily funding readings, oldest first, each carrying its own coverage evidence."
      +    },
      +    "hour_of_day_utc": {
      +      "description": "What a typical hour looks like for this coin, as medians per UTC hour. Absent under 14 recorded days."
      +    },
      +    "liquidations": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Daily forced-close totals."
      +    },
      +    "open_interest": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Daily open interest readings."
      +    },
      +    "pair": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The pair, when the daily market lane was read."
      +    },
      +    "price": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Daily price readings."
      +    },
      +    "stale": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "True only when the lane is further back than its own settle horizon explains."
      +    },
      +    "stale_note": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Present when stale is true: how far past the horizon it has fallen."
      +    },
      +    "whale_flow_daily": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Daily whale buy and sell dollars, when the coin lane was read."
      +    }
      +  },
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: data is archived since specific dates, free plans cap to last day, paid plans reach full archive, and it is descriptive only. The schema further discloses that both lanes settle several days behind live and that `capped` indicates truncation. This goes beyond annotations without contradicting them.

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 sentences, each earning its place: the first defines the two lanes and archive dates, the second explains plan-based access, the third clarifies the descriptive nature. The most decision-relevant information (what data, for what scope) is front-loaded. No fluff or repetition of schema details.

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?

Given the tool has an output schema and 100% schema coverage, the description need not explain return values. It covers the two modes, archive depth, plan limits, and descriptive nature. The only minor gap is that it doesn't explicitly state the 'settles several days behind live' caveat, but that is disclosed in the schema's days parameter, so the description is complete enough for an agent to select and invoke the tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds meaning by framing the two lanes and the archive dates, which helps an agent understand the relationship between coin and pair. The schema itself is unusually rich (explains coin vs pair, defaults, caps, as_of/data_age_days), so the description's added value is moderate but real. It does not repeat the schema verbatim, and it clarifies the 'one pair' vs 'one coin' distinction.

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 names a specific resource (daily market history) and two distinct lanes (pair market data vs coin whale flow), with explicit date ranges. It distinguishes itself from siblings by stating it is 'Descriptive market data only' and by naming the two modes. The verb 'read' is implied but the resource and scope are precise.

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 description states when to use the tool (for daily history of funding, open interest, price, liquidations, or whale flow) and gives plan-based access guidance (free vs paid). It does not explicitly name alternatives among the many siblings, but the two-lane structure and 'Descriptive market data only' hint at when not to use it. The schema descriptions add more usage detail (e.g., coin vs pair selection), but the main description lacks explicit exclusions.

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