Skip to main content
Glama

Central Command

by co.supabase.rtcelwjnrbmfmrywacky

Strategy Language Parser

cc.strategy_data_parser
Read-onlyIdempotent

Call cc.strategy_data_parser — Parses natural language strategy descriptions into structured executable specifications: timeframes, indicators, patterns, risk parameters, and entry/exit rules. Purpose: Parses natural language strategy descriptions into structured executable specifications: timeframes, indicators, patterns, risk parameters, and entry/exit rules. 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.01 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: 20/min (per API key). Tier: standard. Returns: Structured strategy object: TimeframeReq[], IndicatorReq[], PatternReq[], RiskParams, entry_conditions, exit_conditions — ready for backtesting or live execution. Guidelines: Compute / parse / backtest only — no live orders. Feed outputs into cc.agent_strategy with force_paper=true to paper-trade. Tags: parser, nlp, strategy, structured-data, automation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
__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.
descriptionYesNatural language strategy description Required.

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.6/5.0
Behavior5/5

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

The description explicitly states it is read-only, does not place orders or mutate accounts, adds details on authentication, cost ($0.01 per call), rate limit (20/min), and billing context. This amplifies the annotations (readOnlyHint, destructiveHint, idempotentHint) with concrete 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 well-structured with clear sections (purpose, behavior, auth, cost, rate limit, returns, guidelines, tags). It is informative but slightly lengthy; however, every sentence earns its place. Could be slightly more concise but not wasteful.

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 and the presence of annotations and an output schema, the description covers all necessary aspects: behavior, authentication, cost, rate limits, return structure, and usage guidelines. It is fully sufficient 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value for the __x_payment parameter by explaining its usage in retries and that it's not a business parameter, going beyond the schema's description. The description parameter's meaning is sufficiently conveyed.

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 parses natural language strategy descriptions into structured executable specifications, listing specific components (timeframes, indicators, etc.). It distinguishes from sibling tools like cc.agent_strategy and cc.strategy_backtest.

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 clear guidelines: feed outputs into cc.agent_strategy for paper-trading, and states it is for compute/parse/backtest only, not live orders. It implicitly differentiates from execution tools but does not explicitly state when not to use.

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