Skip to main content
Glama

TILLA - market data on one clock

One whole market

tilla_market
Read-onlyIdempotent

One market in one call: every series of market (an id from tilla_markets, e.g. btc, nvda, eurusd, gold) the key holds on lane, on one clock. layer = raw | derived | node | deep | all. related=True adds its connected markets (btc: its ETFs and miners). period = 1d 7d 30d 2m 3m 6m 1y 2y 3y all. At most 200 columns an answer: series_next_offset names the next page. Needs your API key (hosted: the X-API-Key header; local: TILLA_API_KEY).

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>"
    },
    "name": "tilla_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
laneNo1min
layerNoraw
limitNo
marketYes
periodNo
relatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations it discloses two behaviors the agent could not otherwise know: an answer is capped at 200 columns with series_next_offset naming the next page, and the call requires an API key supplied as an X-API-Key header hosted or TILLA_API_KEY locally. That is exactly the kind of pagination and auth detail annotations do not carry.

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?

It is dense and front-loaded, leading with the core promise before enumerating options, and no sentence is padding. The telegraphic notation ('on one clock', 'the key holds on lane') buys brevity at some cost in immediate comprehension.

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 six-parameter, zero-description-schema tool with no output schema, the description covers auth, pagination, and most parameters well. The remaining holes are the unexplained lane values and the unmentioned limit, which matter because nothing in the structured schema fills those gaps.

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?

With schema coverage at 0% and no enums declared, the description does the heavy lifting: it supplies example market ids, the full layer and period value sets, and the meaning of related. However, 'lane' is only named and never explained (the schema merely defaults it to 1min), and 'limit' is not mentioned at all, so two parameters remain undocumented.

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?

The description states a concrete resource and scope: every series a market (btc, nvda, eurusd, gold) has on a given lane, over a period. It distinguishes itself from the sibling tilla_markets by pointing there as the source of valid market ids. It falls short of 5 because the verb is implied rather than stated and the term 'lane' is never defined.

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 clear practical context: how to obtain a market id (from tilla_markets), what related=True does with a concrete example (btc: ETFs and miners), and the allowed layer and period values. It does not say when to prefer it over overlapping siblings such as tilla_window, tilla_latest, tilla_sample or tilla_tick, so the exclusion guidance is missing.

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.