Skip to main content
Glama

Sentinel Aleph

by com.ribqa
OverviewDiscussionsAdmin

Market snapshot

get_market_snapshot
Read-onlyIdempotent

Returns the most recent 4h candles for one scanned symbol, a summary of those inside the last 24h, and the scanner's status. Use it when you need the candle series or data freshness (data_age_seconds); for just the price and window statistics, get_ticker is lighter. limit counts candles back from the newest (100 is about 16 days); the summary covers only returned candles within 24h, so a small limit narrows it. Read from the scanner's in-memory buffer, not a live exchange call: a symbol outside the scanned universe returns an error, and one whose candles are not loaded yet (e.g. just after a restart) returns an error saying to retry after the next scan. No key needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMost recent candles returned.
symbolYesPair to read, e.g. ETHUSDT. Must be in the scanned universe.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoSet only on a failed call (isError true): what went wrong.
symbolNoPair.
candlesNoThe most recent limit candles.
scannerNoScanner state behind the buffer.
summaryNoReturned candles inside the last 24h.
intervalNoCandle interval (4h).
timestampNoResponse time (RFC 3339).
data_sourceNoAlways the scanner buffer.
candle_countNoCandles returned.
data_age_secondsNoSeconds since the newest candle opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "candle_count": {
+      "description": "Candles returned.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "candles": {
+      "description": "The most recent limit candles.",
+      "items": {
+        "description": "One candle.",
+        "properties": {
+          "close": {
+            "description": "Close.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "high": {
+            "description": "High.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "low": {
+            "description": "Low.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "open": {
+            "description": "Open.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "ts": {
+            "description": "Open time (RFC 3339).",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "vol": {
+            "description": "Base-asset volume.",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "data_age_seconds": {
+      "description": "Seconds since the newest candle opened.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "data_source": {
+      "description": "Always the scanner buffer.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Set only on a failed call (isError true): what went wrong.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "interval": {
+      "description": "Candle interval (4h).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "scanner": {
+      "description": "Scanner state behind the buffer.",
+      "properties": {
+        "active_symbols": {
+          "description": "Symbols scanned.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "last_scan": {
+          "description": "Last scan (RFC 3339).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "running": {
+          "description": "Scanner running.",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "scans_total": {
+          "description": "Scans since start.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "signal_count": {
+          "description": "Signals from the current scan.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "summary": {
+      "description": "Returned candles inside the last 24h.",
+      "properties": {
+        "candles": {
+          "description": "Candles summarised.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "change_pct": {
+          "description": "close vs open, percent.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "close": {
+          "description": "Last close.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "first_ts": {
+          "description": "First candle.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "high": {
+          "description": "Highest high.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "last_ts": {
+          "description": "Last candle.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "low": {
+          "description": "Lowest low.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "open": {
+          "description": "First open.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "volume": {
+          "description": "Summed volume.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "window": {
+          "description": "Summary window.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "symbol": {
+      "description": "Pair.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "timestamp": {
+      "description": "Response time (RFC 3339).",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds non-obvious behavior: reads from an in-memory buffer rather than a live exchange call, errors for symbols outside the scanned universe, and a distinct retry-after-next-scan error when candles aren't loaded (e.g. just after restart). It also notes no API key is needed. This is substantial disclosure beyond structured fields.

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-loaded with the return payload first, then usage, then parameter behavior, then failure modes — a logical order with no filler. It is dense and clause-heavy in the middle, but every sentence carries distinct information an agent needs.

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?

With an output schema present, return values need no explanation; the description instead covers the things the schema can't: data freshness (data_age_seconds), the buffer-vs-live distinction, both error conditions, and how limit interacts with the 24h summary. Nothing an agent needs to invoke this correctly is missing.

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%, so baseline is 3, but the description genuinely adds semantics: limit counts back from the newest, 100 ≈ 16 days, and the 24h summary only covers returned candles so a small limit narrows it. That interpretation isn't derivable from the schema's one-line 'Most recent candles returned.'

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 three concrete resources: the most recent 4h candles for one scanned symbol, a 24h summary of those candles, and scanner status. It explicitly distinguishes itself from get_ticker ('for just the price and window statistics, get_ticker is lighter'), so an agent can route between the two without opening either 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?

Gives an explicit when-to-use ('when you need the candle series or data freshness') and names the alternative plus the condition that selects it ('get_ticker is lighter'). It also flags the parameter trade-off that narrows the summary, which is genuine usage guidance rather than restated schema.

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

All Sentinel Aleph 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