Skip to main content
Glama

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

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
pairYes
signalYesThe daily trend
intervalYes
timestampNo
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. 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"
+}
  2. 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"
  3. 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)"
  4. 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)"
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover read-only and open-world, but the description adds important runtime context: a hard 20 calls/hour rate limit, the free tier limitation, and the upstream data sources where the free constraint may matter. It doesn't explain fallback behavior if a pair isn't found on the first exchange, which would push it to a 5.

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?

The first sentence front-loads purpose, output, and source in a dense but readable clause. The second sentence packs five sibling-routing rules efficiently. Slightly long, but every clause earns its place.

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 a 1-parameter tool with an output schema, the description covers purpose, output shape, data provenance, rate limits, and sibling boundaries. An agent could correctly select and invoke this tool without opening any other documentation.

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 coverage is 100% and the schema already documents the pair format including xrpl: prefixes and examples. The description repeats the exchange scope (top 200 coins) and examples but adds no format details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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: daily Ichimoku Cloud trend for a crypto pair, with explicit outputs (bullish/bearish/neutral, cloud position, tenkan/kijun cross) and data sources (Binance.US, Kraken, Gate, MEXC). It clearly distinguishes itself from ichimoku_signal by scoping to the 1d timeframe.

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 routes to alternatives: ichimoku_signal for other timeframes and line values, confluence_signal for six indicators, price_levels for support/resistance, market_scan for all coins, trade_setups for ranked setups. The 20 calls/hour rate limit is also stated, giving concrete usage boundaries.

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