Skip to main content
Glama
Sign In

Ichimoku Signal

by io.github.Fizzl13
OverviewDiscussionsAdmin

Ichimoku daily trend (free)

ichimoku_trend
Read-only

Free: the daily (1d) Ichimoku Cloud trend for a crypto pair (top 200 coins, from Binance.US, Kraken, Gate or MEXC): bullish, bearish or neutral, whether price is above, below or in the cloud, and the tenkan/kijun cross. Limited to 20 calls per hour. For other timeframes and the line values use ichimoku_signal; for six indicators use confluence_signal, for support/resistance and targets price_levels, for every top-200 coin at once market_scan, for ranked trade setups across all coins trade_setups.

Input Schema

NameRequiredDescriptionDefault
pairYesCrypto 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

Output Schema

NameRequiredDescriptionDefault
pairYes
signalYesThe daily trend
exchangeNoWhere the candles come from
intervalYes
timestampNo
candle_timeNoOpening time (UTC) of the latest daily candle; it is still forming, so price is the latest trade
cloud_positionNoabove_cloud, below_cloud or in_cloud
tenkan_kijun_crossNobullish_cross, bearish_cross or none

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / candle_time
      Added value: +{
+  "description": "Opening time (UTC) of the latest daily candle; it is still forming, so price is the latest trade",
+  "type": "string"
+}
    • addedOutput schema / properties / exchange
      Added value: +{
+  "description": "Where the candles come from",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "cloud_position": {
+      "description": "above_cloud, below_cloud or in_cloud",
+      "type": "string"
+    },
+    "interval": {
+      "type": "string"
+    },
+    "pair": {
+      "type": "string"
+    },
+    "signal": {
+      "description": "The daily trend",
+      "enum": [
+        "bullish",
+        "bearish",
+        "neutral"
+      ],
+      "type": "string"
+    },
+    "tenkan_kijun_cross": {
+      "description": "bullish_cross, bearish_cross or none",
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "pair",
+    "interval",
+    "signal"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • 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"
  5. Changed1 schema field changed
    • 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)"
  6. Changed1 schema field changed
    • changedInput schema / properties / pair / description
      Previous value: -"Binance.US spot pair, e.g. BTC-USDT, SOL-USDT or ETHUSDT"New value: +"Crypto pair, e.g. BTC-USDT, SOL-USDT, TAO-USDT or ETHUSDT (Binance.US, then Kraken, then Gate: covers the top 100 coins)"
  7. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, yet the description still adds real behavioral context: a 20 calls/hour rate limit, the four upstream exchanges, the top-200 coin universe, and the explicit absence of line values. It stops short of saying what happens when the rate limit is hit, but the added context is well 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.

Conciseness4/5

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

Purpose is front-loaded ahead of the sibling routing, and every clause carries information. The exchange enumeration and the five-way routing list make it dense, but nothing is redundant with the schema or title.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. The description covers scope, rate limit, sources and alternatives. The only gap is a small stylistic one: the 'free' designation is stated but its practical consequence beyond the rate limit is left implicit.

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%, including xrpl: issuer formats, so the schema already carries the syntax burden. The description still adds meaning by scoping the pair universe to the top 200 coins across four venues, which tells the agent when a pair will resolve. Marginal but genuine value over the schema, so one notch above the high-coverage baseline.

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 — the daily Ichimoku Cloud trend for a crypto pair — and enumerates the exact outputs (bullish/bearish/neutral, cloud position, tenkan/kijun cross). It explicitly distinguishes itself from ichimoku_signal by timeframe and by not returning line values.

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?

Names five sibling tools and the precise condition that selects each: other timeframes/line values → ichimoku_signal, six indicators → confluence_signal, support/resistance → price_levels, all coins at once → market_scan, ranked setups → trade_setups. Routing is explicit with no inference required.

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