Sentinel Aleph

My bots

get_my_bots

Read-onlyIdempotent

Lists up to 100 Special Bots on the API key's account with status and counters: candidates seen, matched, vetoed, signals produced, last result and last evaluation time. Use it to monitor your own bots; for saved strategies use get_my_strategies, for published signals get_open_signals. Takes no arguments; an account without bots gets an empty list. Needs an API key. Read only by design: this server has no bot controls, so deploying, starting, stopping and editing a bot are done in the ribqa.com Market Scanner.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`bots`	No	The account's Special Bots (at most 100).
`count`	No	Bots returned.
`error`	No	Set only on a failed call (isError true): what went wrong.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "bots": {
+      "description": "The account's Special Bots (at most 100).",
+      "items": {
+        "description": "One bot.",
+        "properties": {
+          "bot_mode": {
+            "description": "Bot mode.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "candidates_seen": {
+            "description": "Candidates it evaluated.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Bot id.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "interval": {
+            "description": "Timeframe.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_evaluated_at": {
+            "description": "Last evaluation (RFC 3339), null if never.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_result": {
+            "description": "Last evaluation result.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "market_type": {
+            "description": "spot or futures.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "matched_count": {
+            "description": "Candidates that matched its filters.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "mode": {
+            "description": "Engine mode.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Name.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "signal_count": {
+            "description": "Signals it produced.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "Bot status.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "symbol": {
+            "description": "Pair.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "vetoed_count": {
+            "description": "Matches a veto cancelled.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Bots returned.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Set only on a failed call (isError true): what went wrong.",
+      "type": [
+        "string",
+        "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?

Goes well beyond the annotations: it discloses the 100-item cap, the empty-list behavior for accounts with no bots, the API-key requirement, and the hard design constraint that the server exposes no bot controls (deploy/start/stop/edit happen in the Market Scanner). That last point prevents an agent from hunting for non-existent mutation tools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences, front-loaded with what the tool returns, followed by routing, edge cases, and the read-only design constraint. Every sentence carries distinct information and none is redundant.

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?

Covers auth requirements, result cardinality, the empty-state case, and the absence of write controls. With an output schema present the description needn't explain return formatting, and it doesn't waste space doing so beyond naming the fields.

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?

The tool takes zero arguments, so the baseline is 4. The description confirms this explicitly ('Takes no arguments'), which is a useful affirmation but adds no semantics beyond what the empty schema already conveys.

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 ('Lists up to 100 Special Bots on the API key's account') and immediately enumerates the returned fields (status, counters, last result, last evaluation time). It also names the sibling tools it is not, so an agent can distinguish it from get_my_strategies and get_open_signals without opening a 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 explicit routing: 'Use it to monitor your own bots; for saved strategies use get_my_strategies, for published signals get_open_signals.' The alternative and the condition that selects each one are both stated, leaving nothing 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?