Ichimoku Signal

Confluence signal: 6 indicators ($0.15 via x402)

confluence_signal

Read-only

Paid ($0.15 USDC via x402 on Solana or Base): six indicators for a crypto pair in one call (Ichimoku, RSI 14, MACD 12/26/9, EMA 50/200, Bollinger Bands 20/2, volume OBV), each with its values and a bullish/bearish/neutral vote, plus the combined signal, confidence (high/medium/low), score and a summary like "4 of 6 indicators bullish". Same as GET /signals/{pair}. A "news" field flags recent news (hack, delisting, unlock, legal action) that can break the signal. One pair you already chose; to find which coins have a setup, use trade_setups. Invalid pairs are rejected before payment.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pair`	Yes	Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins). For the XRP Ledger DEX: xrpl:XRP-RLUSD, xrpl:SOLO-XRP, or with the issuer, xrpl:SOLO.rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz-XRP
`interval`	No	Candle interval, default 1h

Output Schema

TableJSON Schema

Name	Required	Description
`news`	No	Only when the news check is on: news from the last 72 hours that can break a technical signal (TypeSafe Jev). The signal itself never changes; treat high as a reason to wait.
`pair`	No	The pair, e.g. BTC-USDT
`price`	No	Last price
`signal`	No	Combined signal of six indicators
`accepts`	No	Only on an unpaid call: the x402 payment options
`summary`	No	e.g. 4 of 6 indicators bearish
`interval`	No	Candle interval, e.g. 1h, 4h, 1d
`timestamp`	No
`confidence`	No	low, medium or high
`indicators`	No	Each indicator with its vote

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

addedOutput schema / properties / news

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {
+        "checked_headlines": {
+          "type": "number"
+        },
+        "headlines": {
+          "description": "Up to 3 recent headlines naming the coin, with url and published",
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "probability": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "risk": {
+          "description": "high: a headline reports a hack, delisting, unlock, legal action or similar for this coin; elevated: maybe; none: nothing found",
+          "enum": [
+            "high",
+            "elevated",
+            "none"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "risk"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Only when the news check is on: news from the last 72 hours that can break a technical signal (TypeSafe Jev). The signal itself never changes; treat high as a reason to wait."
+}

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "accepts": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Only on an unpaid call: the x402 payment options"
+    },
+    "confidence": {
+      "description": "low, medium or high",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "indicators": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Each indicator with its vote"
+    },
+    "interval": {
+      "description": "Candle interval, e.g. 1h, 4h, 1d",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pair": {
+      "description": "The pair, e.g. BTC-USDT",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "description": "Last price",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "signal": {
+      "anyOf": [
+        {
+          "enum": [
+            "bullish",
+            "bearish",
+            "neutral"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Combined signal of six indicators"
+    },
+    "summary": {
+      "description": "e.g. 4 of 6 indicators bearish",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "timestamp": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / pair / description

Previous value: -"Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins)"New value: +"Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins). For the XRP Ledger DEX: xrpl:XRP-RLUSD, xrpl:SOLO-XRP, or with the issuer, xrpl:SOLO.rsoLo2S1kiGeCcn6hCUXVrCpGMWLrRrLZz-XRP"

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / pair / description

Previous value: -"Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, then Gate: covers the top 100 coins)"New value: +"Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, Gate and MEXC: covers the top 200 coins)"

AddedSep 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real burden and delivers: price ($0.15 USDC via x402 on Solana or Base), the no-charge-on-invalid-pair behavior, and the caveat that a 'news' field can invalidate the signal. It doesn't cover rate limits or latency, but the payment/validation behavior is exactly the kind of context annotations can't express.

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?

Front-loads the paid aspect and the payload, then packs outputs, caveats, and routing into a tight block. Dense but nearly every clause carries information; the only mild redundancy is restating output contents when an output schema exists.

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?

Covers cost, payment rails, input format scope, output shape, a risk caveat, and sibling routing. With an output schema present it needn't detail return structure, and nothing an agent needs to invoke it correctly 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?

Schema description coverage is 100%, so both parameters (pair format including XRPL DEX syntax, and the interval enum with its default) are already fully documented in the schema. The description adds no syntax or default detail beyond 'for a crypto pair', so the baseline 3 applies.

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?

States a specific verb+resource ('six indicators for a crypto pair in one call') and enumerates exactly which indicators (Ichimoku, RSI 14, MACD, EMA, Bollinger, OBV), so an agent can distinguish it from the sibling single-indicator tools like ichimoku_signal without opening a schema.

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?

Explicitly scopes usage: 'One pair you already chose; to find which coins have a setup, use trade_setups.' That names the alternative and the condition that selects it. It also notes invalid pairs are rejected before payment, which removes a hesitation about calling it speculatively.

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

All Ichimoku Signal 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?