Skip to main content
Glama

Central Command — x402 Trading Intelligence

by io.github.tlefko

AI Trading Chat

cc.squirrel_chat
Read-onlyIdempotent

Call cc.squirrel_chat — Full AI trading assistant with real-time market data, position analysis, chart drawing commands, and multi-tool execution. Supports 60+ data actions including candles, funding rates, open interest, liquidations, order book, and more. Returns structured analysis with optional chart annotations. Purpose: Full AI trading assistant with real-time market data, position analysis, chart drawing commands, and multi-tool execution. Supports 60+ data actions including candles, funding rates, open interest, liquidations, order book, and more. Returns structured analysis with optional chart annotations. Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account. Live / near-real-time data. Auth: X-Api-Key or x402 payment proof (X-PAYMENT / __x_payment). Anonymous unauthenticated calls receive HTTP 402 with payment accepts. Cost: $0.002 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: 10/min (per API key). Tier: premium. Returns: AI response with market analysis, trade suggestions, and optional draw_commands for chart annotations. Token usage included for billing. Guidelines: Pass required parameters exactly; omit unknown fields. On 402, settle payment then retry with X-PAYMENT. Tags: chat, ai, analysis, trading, market-data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoActive chart symbol (e.g. BTC-USDT) Optional.
messageYesUser message / question / instruction Required.
positionsNoCurrent open positions for context Optional.
timeframeNoActive chart timeframe (e.g. 4H) 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.
conversation_idNoExisting conversation UUID for context continuity 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

A3.6/5.0
Behavior5/5

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

The description goes far beyond the annotations by explicitly stating 'Behavior: READ-ONLY. Does not place orders, move funds, or mutate your exchange account', and also discloses auth methods (X-Api-Key or x402), cost per call, rate limits, and retry behavior on 402. This provides rich behavioral context that annotations alone do not cover, and it is consistent with the readOnlyHint=true annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and contains significant redundancy. The 'Purpose:' section repeats the opening sentence verbatim, and the 'Tags:' section adds little new information. While the labeled sections (Behavior, Auth, Cost, Rate limit, Returns, Guidelines) improve structure, the duplication and extra length reduce conciseness.

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?

For a complex tool with auth, payment, and rate-limiting considerations, the description is exceptionally complete. It covers operational requirements (X-Api-Key / x402), cost per call, rate limits, return format, and specific error-handling instructions ('On 402, settle payment then retry with X-PAYMENT'). Combined with a rich output schema and thorough annotations, nothing essential is missing.

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?

The input schema already covers all six parameters with descriptions (100% coverage), so the baseline is 3. The description adds minimal semantic value for parameters beyond noting that the message can request 60+ data actions and clarifying that __x_payment is 'not a business parameter', but these nuances exist in the schema as well. It does not compensate further for parameter usage.

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 clearly identifies the tool as a 'Full AI trading assistant' with real-time market data, position analysis, chart drawing commands, and multi-tool execution, and lists 60+ data actions. However, it does not explicitly distinguish itself from sibling chat tools like cc.squirrel_chat_v2 or cc.openclaw_chat, missing an opportunity for differentiation.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives. It lists supported capabilities and gives operational guidelines for parameters and 402 retries, but does not state when to choose this over dedicated data tools (e.g., cc.funding_rates) or other chat tools. Usage is only implied through the feature list, not explicitly stated.

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

All Central Command — x402 Trading Intelligence 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

A3.7/5.0
Disambiguation2/5

Multiple tools have overlapping or unclear boundaries. The AI chat tools cc.squirrel_chat, cc.squirrel_chat_v2, and cc.openclaw_chat all provide conversational trading assistance with near-identical descriptions, while cc.central_signal and cc.external_signal both normalize signals for execution. Additionally, cc.asset_scanner, cc.auto_fetch_market_data, cc.data_tools, and cc.ma_fetch all supply technical indicator data with significant overlap.

Naming Consistency4/5

All tools share the 'cc.' prefix and use snake_case consistently, which creates a uniform feel. However, naming style mixes nouns (cc.asset_scanner, cc.data_tools) with verbs (cc.auto_fetch, cc.list_catalog) and compound forms (cc.strategy_backtest, cc.trade_builder), so it is not a strict verb_noun pattern. Minor deviations keep it from a 5.

Tool Count2/5

With 33 tools, the server is well beyond the typical well-scoped range of 3-15 and even above the 'heavy' 16-25 range. While the trading intelligence domain can be broad, this count feels overstuffed rather than curated, especially given the many overlapping data and AI tools.

Completeness3/5

The core trading workflow is covered: market data, technical analysis, signals, strategy backtesting, paper trading, and live execution all have tools. However, there is no dedicated account management tool (e.g., get_balance, list_positions) and no explicit delete_strategy, with these operations buried inside cc.agent_strategy's action parameter. Notable gaps remain for a complete lifecycle.

Resources