Skip to main content
Glama

tape

Read-onlyIdempotent

Read real candles from the Taifoon tape for one market. Use it to ground an answer in what the market actually did in a past window — never to predict. NQ is not continuous (weekend halt, 21:00 UTC daily break). A past window is SEALED: its bars never change, so cache it. The same tape is open over plain HTTP with no key: GET https://clob.taifoon.dev/tape/v1/candles/{market}/{tf}?from=&to= with unix SECONDS and a User-Agent that names you (OpenAPI: https://www.taifoon.io/clob/openapi.yaml). It is the tape the coordination layer's conformance check replays, so what you read here is what the judge reads.

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": {
      "market": "<market>",
      "tf": "<tf>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "tape"
  }
}

Input Schema

NameRequiredDescriptionDefault
tfYestimeframe (the time machine serves these)
toYeswindow end, ISO-8601 UTC, in the past
fromYeswindow start, ISO-8601 UTC
marketYesthe market

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tf / enum
      Previous value: -[
      -  "15s",
      -  "1m",
      -  "5m",
      -  "15m",
      -  "1h",
      -  "4h",
      -  "1d"
      -]New value: +[
      +  "1s",
      +  "15s",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "1h",
      +  "4h",
      +  "1d"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / tf / description
      Previous value: -"timeframe (the time machine serves these; build a 15-minute range from 1m or 5m bars)"New value: +"timeframe (the time machine serves these)"
    • changedInput schema / properties / tf / enum
      Previous value: -[
      -  "15s",
      -  "1m",
      -  "5m",
      -  "1h"
      -]New value: +[
      +  "15s",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "1h",
      +  "4h",
      +  "1d"
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it warns that NQ has a weekend halt and a 21:00 UTC daily break, that past windows are immutable and therefore cacheable, that the same data is reachable over unauthenticated HTTP, and that this tape is what the conformance check replays. That is substantive operational context the readOnly/idempotent hints do not convey.

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 with the action and the intent, then the operational caveats. The HTTP/OpenAPI sentence is longer than strictly necessary for calling the MCP tool, but it is genuinely useful fallback information rather than filler.

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?

With no output schema, the description should hint at return shape; it says 'real candles' and that bars are immutable but never names the candle fields or any row limit for large windows. For a four-required-param read tool, that is the one remaining gap.

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 coverage is 100% with enums for market and tf, so the baseline is 3. The description adds that the window must be in the past and that sealed windows are immutable, but it does not clarify the relationship between the MCP ISO-8601 from/to parameters and the 'unix SECONDS' format cited for the HTTP endpoint, which could mislead an agent about the argument format.

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?

States a specific verb and resource ('Read real candles from the Taifoon tape') with an explicit scope ('for one market'), which clearly separates it from siblings like price, chart_state, and digest that also surface market data.

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?

Gives a clear when-to-use rule ('ground an answer in what the market actually did in a past window') and an explicit exclusion ('never to predict'), plus a caching hint for sealed windows. It stops short of naming a sibling alternative (e.g. live price vs. historical tape), which keeps it from a 5.

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