Skip to main content
Glama

Bitfinex

by io.github.pipeworx-io

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / claim_token
      Added value: +{
+  "description": "Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "type",
-  "message"
-]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which only indicate readOnly=false), the description discloses rate limits ('Rate-limited to 5 per identifier per day'), the claim_token workflow for reading replies, cost ('Free; doesn't count against your tool-call quota'), and the team's daily digest reading. This is rich behavioral context.

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?

The description is lengthy but each sentence adds distinct value: purpose, use cases, exclusions, claim_token mechanics, rate limits, pricing. It's front-loaded with the core purpose and efficiently packs a lot of guidance into a single paragraph, though it could use structural breaks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 explains return behavior: filing 'returns a `claim_token`' and reading 'returns the status and, once resolved, what actually changed.' It also covers scope, limitations, and the dual-mode operation, making it fully self-contained.

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?

The input schema already has 100% coverage with descriptions for all four parameters. The description adds extra semantics for claim_token by giving a concrete usage example: 'pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed.' It also clarifies that no parameters are required, which is helpful for the read-flow.

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 clearly states the tool's function: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It distinguishes from siblings by specifying it's for feedback about Pipeworx tools only, contrasting with ask_pipeworx or other tools, and even clarifies not to use for other MCP servers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use conditions: 'Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise).' It also gives a clear exclusion: 'if the tool came from a different MCP server... file it with that server instead.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bitfinex toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation2/5

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.

Naming Consistency2/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Resources