Central Command — x402 Trading Intelligence

AI Indicator Creator

cc.indicator_generator

Read-onlyIdempotent

Call cc.indicator_generator — AI-powered indicator workshop. Actions: generate (prompt→code), list_library (user saved indicators), get_indicator (by id), delete_indicator, get_draft (poll generation status), save (persist to library). Returns full indicator code, params, and metadata. Purpose: AI-powered indicator workshop. Actions: generate (prompt→code), list_library (user saved indicators), get_indicator (by id), delete_indicator, get_draft (poll generation status), save (persist to library). Returns full indicator code, params, and metadata. 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.02 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: For generation: {success, processing, generation_id}. For list_library: {indicators:[{id, name, description, code, color, is_overlay, params}]}. For get_draft: {draft, status, generation_id}. Guidelines: Pass required parameters exactly; omit unknown fields. On 402, settle payment then retry with X-PAYMENT. Tags: indicator, code-generation, ai, custom, technical-analysis, charting.

Input Schema

TableJSON Schema

Name	Required	Description
`save`	No	Set true with indicator_data to persist to library Optional.
`action`	No	list_library \| get_indicator \| delete_indicator \| get_draft \| save. Omit for generation. Optional.
`prompt`	No	Natural language description of indicator to generate (required for generation) Optional.
`history`	No	Conversation history for refinement Optional.
`timeframe`	No	Chart timeframe context (e.g. 4H, 1D) Optional.
`__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.
`indicator_id`	No	UUID of indicator (for get/delete actions) Optional.
`indicator_data`	No	Full indicator object to save: {name, description, code, color, is_overlay, params} Optional.

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).

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedJul 25, 2026

addedInput schema / properties / action

Added value: +{
+  "description": "list_library | get_indicator | delete_indicator | get_draft | save. Omit for generation. Optional.",
+  "type": "string"
+}

removedInput schema / properties / description

Removed value: -{
-  "description": "What the indicator should do Required.",
-  "type": "string"
-}

addedInput schema / properties / history

Added value: +{
+  "description": "Conversation history for refinement Optional.",
+  "type": "array"
+}

addedInput schema / properties / indicator_data

Added value: +{
+  "description": "Full indicator object to save: {name, description, code, color, is_overlay, params} Optional.",
+  "type": "object"
+}

addedInput schema / properties / indicator_id

Added value: +{
+  "description": "UUID of indicator (for get/delete actions) Optional.",
+  "type": "string"
+}

addedInput schema / properties / prompt

Added value: +{
+  "description": "Natural language description of indicator to generate (required for generation) Optional.",
+  "type": "string"
+}

addedInput schema / properties / save

Added value: +{
+  "description": "Set true with indicator_data to persist to library Optional.",
+  "type": "boolean"
+}

removedInput schema / properties / style

Removed value: -{
-  "description": "overlay, oscillator, histogram Optional.",
-  "type": "string"
-}

addedInput schema / properties / timeframe

Added value: +{
+  "description": "Chart timeframe context (e.g. 4H, 1D) Optional.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "description"
-]New value: +[]

changedOutput schema / description

Previous value: -"Structured MCP result envelope. `data` holds the endpoint JSON payload. Endpoint returns: JSON: name, description, color, is_overlay, configurable_params, executable_code (JS function body), and explanation of the logic."New value: +"Structured MCP result envelope. `data` holds the endpoint JSON payload. Endpoint returns: For generation: {success, processing, generation_id}. For list_library: {indicators:[{id, name, description, code, color, is_overlay, params}]}. For get_draft: {draft, status, generation_id}."

AddedJul 24, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond annotations, the description discloses that the tool is READ-ONLY with respect to the exchange account, and details auth requirements, cost, rate limits, and HTTP 402 handling. It clearly distinguishes billing from side effects, adding significant context.

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 the core purpose, but it repeats the actions list twice, making it redundant. The inclusion of tags and repetitive phrases means some sentences do not earn their place.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex with multiple actions and an output schema, but the description covers auth, rate limits, cost, return types, and error handling. It lacks explicit per-action parameter mappings, but the schema and action names make it inferable.

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 provides descriptions for all 8 parameters, so the baseline is 3. The description adds minimal extra semantic detail, only vaguely referencing 'prompt→code' and generic guidance like 'Pass required parameters exactly'.

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 that this is an 'AI-powered indicator workshop' and enumerates specific actions (generate, list_library, get_indicator, delete_indicator, get_draft, save). It distinguishes itself from sibling tools by focusing on custom indicator generation rather than market data or strategy execution.

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 context for when to use the tool and lists distinct actions for various use cases. However, it does not explicitly mention alternatives or exclusion criteria, so the 'when not to use' guidance is missing.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?