ticker_historyBitfinex crypto exchange — historical ticker snapshots for one or more pairs (comma-separated symbols like 'tBTCUSD'). Optional start/end (ms epoch) and limit. Returns bid/ask/last per timestamp.
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | ||
| limit | No | ||
| start | No | ||
| symbols | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of items returned. | |
| items | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: the exchange source, symbol format, epoch time units, and the return fields (bid/ask/last per timestamp), which enrich the agent's understanding.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, information-dense sentence that front-loads the core purpose and includes only essential details. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the rich annotations (read-only, open-world, idempotent), the presence of an output schema, and the compact description covering purpose, key parameters, and return shape, the tool is sufficiently complete for an agent to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description carries the burden for parameter meaning. It explains 'symbols' with an example format, 'start/end' as ms epoch, and 'limit' as an optional count, effectively compensating for the empty schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('historical ticker snapshots') for a specific resource (Bitfinex pairs), clearly distinguishing it from sibling tools like current ticker, candles, or trades. The mention of one or more comma-separated pairs further clarifies scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It clearly implies use for historical data retrieval with optional start/end and limit, making the intended scenario evident. However, it does not explicitly name alternatives or state when not to use it, leaving some implicit differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools overlap or are near-duplicates: ask_pipeworx and ask_pipeworx_beta are currently identical, and there are multiple prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) with fine-grained but confusing distinctions. The mix of Bitfinex market data tools with an unrelated Pipeworx research suite makes tool selection genuinely ambiguous.
All names use lowercase snake_case, but the semantic pattern is inconsistent: bare nouns (ticker, candles, trades, stats), verb_noun phrases (validate_claim, compare_entities, generate_llms_txt), and large prefixed families (ask_pipeworx*, polymarket_*) coexist. This mixed convention gives no reliable cue to a tool's function.
42 tools is excessive for a server named 'Bitfinex'. Only about a dozen tools actually relate to the crypto exchange (ticker, candles, trades, book, liquidations, etc.); the rest are a grab bag of Pipeworx research, prediction markets, memory, and subscription features. The count bloats the surface and obscures the server's purpose.
The set has no coherent scope. For a Bitfinex server, there are no account/trading tools, only market data. For the buried Pipeworx functionality, the surface is extensive but unrelated to Bitfinex. The overall result is an incomplete hodgepodge with no clear lifecycle or workflow for a single domain.