Sentinel Aleph

Ticker

get_ticker

Read-onlyIdempotent

Returns the last price and open, high, low, close, volume and change % over a window for one scanned symbol. Use it for a quick price check; for the candles themselves or the scanner's freshness, use get_market_snapshot. window_hours is counted in whole 4h candles from the scanner buffer (24 uses 6; candles_used says how many), so short windows move in 4-hour steps. A symbol outside the scanned universe returns an error, as does one whose candles are not loaded yet (e.g. just after a restart; retry after the next scan). No key needed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Pair to read. Must be in the scanned universe.
`window_hours`	No	Statistics window in hours.

Output Schema

TableJSON Schema

Name	Required	Description
`low`	No	Window low.
`high`	No	Window high.
`open`	No	Window open.
`close`	No	Window close.
`error`	No	Set only on a failed call (isError true): what went wrong.
`price`	No	Last close.
`period`	No	Statistics window.
`symbol`	No	Pair.
`volume`	No	Window volume, base asset.
`timestamp`	No	Response time (RFC 3339).
`change_pct`	No	close vs open, percent.
`data_source`	No	Always the scanner buffer.
`candles_used`	No	4h candles inside the window.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "candles_used": {
+      "description": "4h candles inside the window.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "change_pct": {
+      "description": "close vs open, percent.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "close": {
+      "description": "Window close.",
+      "type": [
+        "number",
+        "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"
+      ]
+    },
+    "high": {
+      "description": "Window high.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "low": {
+      "description": "Window low.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "open": {
+      "description": "Window open.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "period": {
+      "description": "Statistics window.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "description": "Last close.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "symbol": {
+      "description": "Pair.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "timestamp": {
+      "description": "Response time (RFC 3339).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "volume": {
+      "description": "Window volume, base asset.",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial extra context: window bucketing, error conditions for out-of-universe symbols and unloaded candles, retry guidance after a restart, and the no-auth note. This is well beyond what annotations provide.

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 shape and the alternative tool, and every sentence carries information. Slightly dense with multiple clauses stacked, but no filler.

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 fields need not be spelled out; the description instead covers error behavior, window semantics, and tool routing. Complete for a two-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description adds real semantics beyond the schema: window_hours is counted in whole 4h candles (24 uses 6, candles_used reports the count) so short windows move in 4-hour steps. This explains a non-obvious behavioral quirk the schema does not convey.

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 (returns last price, OHLC, volume, change %) scoped to one scanned symbol, and explicitly distinguishes itself from the sibling get_market_snapshot. An agent can tell exactly what this returns versus the candle/snapshot tool.

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 explicit when-to-use ('quick price check') and names the alternative for the other case ('for the candles themselves or the scanner's freshness, use get_market_snapshot'). 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 Sentinel Aleph tools Inspect

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

Need Help?