Skip to main content
Glama

Ichimoku Signal

by io.github.Fizzl13
OverviewDiscussionsAdmin

Market scan: every top-200 coin ($0.10 via x402)

market_scan
Read-only

Paid ($0.10 USDC via x402 on Solana or Base): the Ichimoku Cloud signal for 148 top-200 coins (stablecoins excluded) in one call, sorted from strongest bullish to strongest bearish by the price's distance from the cloud, with market breadth ("69 of 147 coins bullish") and per coin the signal, price, cloud position, tenkan/kijun cross and exchange. Optional filter on bullish, bearish or neutral. Ichimoku only, no trade plans: for the market's direction at a glance; for coins with entry, stop and targets use trade_setups. Same as GET /scan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signalNoOnly return coins with this signal
intervalNoCandle interval, default 1h

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinsNoEvery coin, strongest bullish first
acceptsNoOnly on an unpaid call: the x402 payment options
breadthNoe.g. 71 of 148 coins bearish
intervalNo
timestampNo
coins_scannedNo

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"
+    },
+    "breadth": {
+      "description": "e.g. 71 of 148 coins bearish",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "coins": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Every coin, strongest bullish first"
+    },
+    "coins_scanned": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "interval": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "timestamp": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, but the description adds the crucial non-obvious context: this call is paid ($0.10 USDC via x402 on Solana or Base) and the universe excludes stablecoins. That is real added value beyond structured fields. It stops short of stating rate limits or what happens on payment failure, and the coin count is internally inconsistent (148 vs '69 of 147'), keeping it from 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?

A single front-loaded sentence that leads with the payment requirement, then the payload, then the alternative-tool routing. Every clause carries information, though the density (payment rails, exclusions, breadth, per-coin fields, filter, sibling contrast all in one breath) makes it slightly hard to scan.

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?

An output schema exists, so return values need not be spelled out, yet the description still conveys the sort order, breadth summary, per-coin fields and optional filter. Combined with the disclosed cost and payment rails for a paid open-world read tool, an agent has everything needed to call it correctly.

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 are already documented in the schema — the baseline is 3. The description restates the signal filter's semantics (bullish/bearish/neutral) but adds nothing about the interval parameter or the interaction between the two, so it does not exceed the schema.

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 (Ichimoku Cloud signal for 148 top-200 coins) with an explicit scope note that stablecoins are excluded and the result is sorted strongest-bullish to strongest-bearish. It also names the sibling it is not (trade_setups) and the endpoint it mirrors (GET /scan), so an agent can distinguish it without opening the 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?

Explicit routing: use this for the market's direction at a glance; use trade_setups when entry, stop and targets are needed. The optional bullish/bearish/neutral filter is also described as a usage condition. Nothing is left to inference.

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