Central Command

TWAP Order Executor

cc.twap_executor

Destructive

Call cc.twap_executor — Time-Weighted Average Price execution engine — splits large orders into smaller randomized slices over configurable time windows to minimize market impact. Purpose: Time-Weighted Average Price execution engine — splits large orders into smaller randomized slices over configurable time windows to minimize market impact. Behavior: DESTRUCTIVE. Splits and submits real exchange orders over time. Irreversible fills once slices execute. Not a simulation. Auth: X-Api-Key required (and linked exchange credentials for execution actions). Cost: $0.015 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: Execution status: filled slices, average fill price, remaining quantity, estimated completion time. Guidelines: Prefer paper/simulation paths. For live money require explicit human confirmation (confirm_live / action=execute). Report real HTTP errors; never invent proxy failures. Tags: execution, twap, smart-order, market-impact, slippage.

Input Schema

TableJSON Schema

Name	Required	Description
`side`	Yes	Parameter `side` (string). Required.
`slices`	No	Parameter `slices` (number). Optional.
`symbol`	Yes	Parameter `symbol` (string). Required.
`total_size`	Yes	Parameter `total_size` (number). Required.
`__x_payment`	No	Optional 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.
`duration_minutes`	Yes	Parameter `duration_minutes` (number). Required.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when the gateway HTTP status is 2xx.
`data`	No	Parsed JSON body from the endpoint (shape varies by slug).
`error`	No	Error message when ok is false.
`status`	Yes	Upstream HTTP status from x402-gateway.
`billing`	No	Optional payment / cost metadata when present.
`endpoint`	Yes	Catalog slug that was invoked (e.g. funding-rates).

TDQS

A4.7/5.0

Behavior5/5

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

The description explicitly states the tool is destructive, submits real exchange orders irreversibly, and is not a simulation. It also clarifies cost as billing (not a side effect) and mentions auth and rate limits, adding context beyond the annotations.

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

Conciseness3/5

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

The description is front-loaded with purpose but contains redundancy: the purpose sentence is repeated verbatim. It is longer than necessary, which slightly reduces 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?

Despite having an output schema, the description still explains return values (filled slices, average price, etc.). It covers all important aspects: purpose, behavior, auth, cost, rate limits, guidelines, and tags, making it highly complete for a complex execution tool.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds context for parameters (e.g., 'slices', 'duration_minutes') by explaining the randomization and time window concept, but does not provide deep semantic meaning for each parameter beyond what the schema already offers.

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 is a Time-Weighted Average Price execution engine that splits large orders into randomized slices over time windows to minimize market impact. This specific verb-resource pair distinguishes it from sibling tools, which are primarily data or analysis tools.

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?

Explicit guidelines are provided: prefer paper/simulation paths, require human confirmation for live money, and mention auth requirements and rate limits. This gives clear when-to-use and when-not-to-use advice.

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

All Central Command tools Inspect

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

Need Help?