Skip to main content
Glama

Central Command

by co.supabase.rtcelwjnrbmfmrywacky

BloFin Public Market Data

cc.blofin_public
Read-onlyIdempotent

Call cc.blofin_public — Proxy to BloFin public API (tickers, instruments, orderbook, trades, candles) bypassing CORS restrictions. Purpose: Proxy to BloFin public API (tickers, instruments, orderbook, trades, candles) bypassing CORS restrictions. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Responses may be cached (~60s). Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.0005 USDC per successful call (x402 Base USDC pay-per-use or prepaid X-Api-Key balance). Linked Connect keys are free. This is billing, not a side effect. Rate limit: 120/min (per API key). Tier: standard. Returns: Raw BloFin public API response for any public endpoint: real-time tickers, full orderbook depth, recent trades, OHLCV candles. Guidelines: Pass required parameters exactly; omit unknown fields. On 402, settle payment then retry with X-PAYMENT. Tags: blofin, orderbook, tickers, candles, exchange-data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesBloFin API path e.g. /api/v1/market/tickers Required.
paramsNoParameter `params` (object). Optional.
__x_paymentNoOptional x402 payment proof (same value as X-PAYMENT header). Use when retrying after HTTP 402 if your MCP client cannot set custom headers. Not a business parameter. Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when the gateway HTTP status is 2xx.
dataNoParsed JSON body from the endpoint (shape varies by slug).
errorNoError message when ok is false.
statusYesUpstream HTTP status from x402-gateway.
billingNoOptional payment / cost metadata when present.
endpointYesCatalog slug that was invoked (e.g. funding-rates).

TDQS

A4.4/5.0
Behavior5/5

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

The description goes well beyond annotations by detailing caching (~60s), auth requirements (X-Api-Key or x402), billing ($0.0005/call), rate limit (120/min), and error handling (402 payment). It explicitly states read-only behavior, no mutation. No contradiction with annotations.

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 somewhat long but well-structured with clear sections and no wasted sentences. It efficiently packs essential info without being overly verbose.

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?

Given the tool's complexity (3 params, 1 required, output schema present), the description covers billing, rate limits, auth, caching, error handling, and return type. It is fully self-contained for an agent to use correctly.

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?

With 100% schema coverage, the description adds marginal value: it reiterates path example and payment retry context. The schema already documents all three parameters adequately, so baseline 3 is appropriate.

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 explicitly states the tool is a proxy to BloFin public API for market data (tickers, instruments, orderbook, trades, candles) bypassing CORS. This clearly distinguishes it from sibling tools which serve other exchanges or data types.

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?

The description provides guidelines on when to use (to get public market data without CORS) and how to use (pass parameters exactly, omit unknown fields, retry with payment on 402). It lacks explicit discussion of when not to use or alternative tools, but the context is clear enough.

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

All Central Command 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

A4.1/5.0
Disambiguation2/5

Many tools serve overlapping purposes, such as multiple Coinglass data tools (cc.coinglass_data, cc.funding_rates, cc.open_interest, etc.) and multiple AI chat assistants (cc.squirrel_chat, cc.squirrel_chat_v2, cc.openclaw_chat). The distinctions are subtle, likely causing agent misselection.

Naming Consistency5/5

All tool names follow a consistent `cc.<snake_case>` pattern, with verbs like `list_catalog`, `cc.ma_fetch`, and `cc.trade_builder`. No mixing of conventions.

Tool Count3/5

33 tools is on the high side but reasonable for a comprehensive crypto trading platform. However, significant redundancy (e.g., multiple data sources for similar indicators) suggests some could be consolidated, making the surface feel heavier than necessary.

Completeness4/5

The tool set covers most aspects of crypto trading: market data, technical indicators, signals, execution, backtesting, AI analysis, and blockchain RPC. Minor gaps exist (e.g., portfolio management), but the surface is largely complete for the intended domain.

Resources