Skip to main content
Glama
Sign In

Ichimoku Signal

by io.github.Fizzl13
OverviewDiscussionsAdmin

Trade setups: every top-200 coin, ranked ($0.50 via x402)

trade_setups
Read-only

Paid ($0.50 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, in RLUSD on the XRP Ledger, or in USD₮0 on X Layer): which crypto coins have a trade setup right now. For 148 top-200 coins: the six-indicator confluence signal (Ichimoku, RSI, MACD, EMA 50/200, Bollinger, OBV) and a trade plan in that direction (entry, stop, two take profit targets, risk/reward), ranked by signal strength x risk/reward, lower for high volatility, for support/resistance right after the entry and for thinly traded coins. Filters: direction (long/short/both), min_rr, top, liquid_top (only the N most traded coins). The screener across all coins; for one pair you already chose use confluence_signal and price_levels. Same as GET /setups. Levels from price history, not trade advice. A screener, not a strategy: in our backtest these setups did no better than random entries after fees.

Input Schema

NameRequiredDescriptionDefault
topNoHow many setups to return (default 10)
min_rrNoMinimum risk/reward to target 1 (default 1.5)
intervalNoCandle interval, default 4h
directionNoOnly long or only short setups (default both)
liquid_topNoOnly the N most traded coins, e.g. 30 (default all)

Output Schema

NameRequiredDescriptionDefault
setupsNoRanked setups with entry, stop and targets
acceptsNoOnly on an unpaid call: the x402 payment options
intervalNo
timestampNo
setups_foundNo
coins_scannedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / accepts / anyOf
      Previous value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / setups / anyOf
      Previous value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed1 schema field changed
    • 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"
+    },
+    "coins_scanned": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "interval": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "setups": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Ranked setups with entry, stop and targets"
+    },
+    "setups_found": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "timestamp": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / liquid_top
      Added value: +{
+  "description": "Only the N most traded coins, e.g. 30 (default all)",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond readOnlyHint/openWorldHint: it discloses the paid access model ($0.50 via x402, with the full list of chains and payment tokens), the ranking formula, the down-weighting factors for volatility, nearby support/resistance and thin liquidity, and an honest backtest caveat. Minor gap: no mention of rate limits, retries or failure behavior when payment fails.

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?

Dense but purposeful, with no filler sentences. However, the long parenthetical enumerating eight chains and three stablecoins occupies the very front of the description, pushing the actual purpose into second position; a short purpose statement before the payment detail would improve front-loading.

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 5 optional params, full schema coverage, and an output schema that carries the return shape, the description supplies everything an agent needs: what it screens, how results are ranked, cost/payment mechanism, and a candid accuracy disclaimer.

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 the schema already documents top, min_rr, interval, direction and liquid_top. The description names the filters and gives one example ('e.g. 30' for liquid_top is in the schema) but adds no new meaning such as how min_rr interacts with the two take-profit targets, and interval is never mentioned. 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 and resource ('which crypto coins have a trade setup right now') plus scope ('for 148 top-200 coins' and the six indicators behind the signal). It explicitly separates itself from siblings: 'The screener across all coins; for one pair you already chose use confluence_signal and price_levels.'

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?

Gives explicit when-to-use and when-not-to-use guidance with named alternatives (confluence_signal, price_levels for an already-chosen pair), and even frames the tool's limits ('A screener, not a strategy'). The filter list (direction, min_rr, top, liquid_top) shows how to narrow usage without opening the schema.

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

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