Skip to main content
Glama

Ichimoku Signal

by io.github.Fizzl13
OverviewDiscussionsAdmin

Price levels and a long/short plan ($0.05 via x402)

price_levels
Read-only

Paid ($0.05 USDC via x402 on Solana or Base): price levels for a crypto pair: up to 3 supports and resistances (swing highs/lows and pivots), ATR, pivots, Fibonacci retracements and Ichimoku levels, the bias from the confluence signal, and a long and a short plan (entry, stop, two targets, risk/reward). Same as GET /levels/{pair}. Levels from price history, not trade advice. One pair; for ranked plans across all coins use trade_setups. Invalid pairs are rejected before payment.

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
intervalNoCandle interval, default 1h

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
biasNolong, short or neutral, from the confluence signal
pairNoThe pair, e.g. BTC-USDT
priceNoLast price
acceptsNoOnly on an unpaid call: the x402 payment options
intervalNoCandle interval, e.g. 1h, 4h, 1d
supportsNo
timestampNo
resistancesNo

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": {
+    "accepts": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Only on an unpaid call: the x402 payment options"
+    },
+    "bias": {
+      "description": "long, short or neutral, from the confluence signal",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+      ]
+    },
+    "resistances": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "supports": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "timestamp": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "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. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds substantial context: the $0.05 USDC x402 payment on Solana or Base, that validation happens before payment is charged, and the 'levels from price history, not trade advice' disclaimer. This is meaningful disclosure beyond the annotations, though payment-failure/refund behavior isn't detailed.

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 payment cost and the core resource, then packs output details into one dense sentence. Every clause carries information, though the single run-on sentence is heavy to parse.

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 needn't be re-explained, yet the description helpfully summarizes the payload. Payment model, alternative tool, and rejection behavior are covered; only edge cases like timeout or partial-failure handling are absent.

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% and both parameters (pair, interval) are thoroughly documented in the schema itself, so the schema carries the burden. The description only adds the 'one pair' constraint and the GET /levels/{pair} mapping, which is minor added value.

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 resource (price levels for a crypto pair) and enumerates the concrete outputs — supports/resistances, ATR, pivots, Fibonacci, Ichimoku, bias, and long/short plans — so an agent knows exactly what this returns. It also distinguishes itself from the sibling trade_setups by scoping to one pair.

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?

Explicitly names the alternative ('for ranked plans across all coins use trade_setups') and states the single-pair constraint, plus that invalid pairs are rejected before payment. It gives clear context for use but doesn't spell out when-not conditions beyond the pair scoping.

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