bookBitfinex crypto exchange order book (bids + asks) for a crypto pair like "tBTCUSD". Returns price levels with size + count. Use for live depth-of-book analysis, spread, market microstructure.
| Name | Required | Description | Default |
|---|---|---|---|
| length | No | ||
| symbol | Yes | ||
| precision | No |
| 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 readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the return format (price levels with size + count) and emphasizes 'live' data, but does not disclose behavior like default length, precision semantics, or error handling. This is adequate but not rich.
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 two sentences, front-loaded with the core purpose, followed by return format and usage. Every sentence earns its place with no redundant or filler content.
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?
Despite having annotations and an output schema, the input schema is bare and the description fails to explain key parameters and behavioral defaults. The tool is moderately complex (3 params), and the description only addresses the purpose and usage, leaving significant gaps in how to 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 must explain all parameters. It only hints at the meaning of 'symbol' via the example 'tBTCUSD', and completely fails to explain 'length' and 'precision'. The example in the schema (length:25, precision:'P0') is not elaborated, leaving the agent without necessary parameter semantics.
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 clearly identifies the tool as returning the Bitfinex order book (bids + asks) for a specific crypto pair, with a concrete example. It distinguishes itself from sibling market data tools (e.g., ticker, trades, candles) by specifying depth-of-book data with price levels, size, and count.
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?
The description provides explicit use cases: 'live depth-of-book analysis, spread, market microstructure.' This gives clear context for when to use the tool, though it does not mention when not to use it or point to alternatives, which would earn a 5.
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.