Sentinel Aleph

My strategies

get_my_strategies

Read-onlyIdempotent

Lists the saved strategies on the API key's account, newest first, archived ones included (active false): id, mode, engines, minimum confidence, direction and symbols. Use it to pick the strategy_id that run_backtest, update_strategy and delete_strategy take; for live bot activity use get_my_bots. Archived strategies count toward limit, and there is no paging: a strategy beyond the newest limit is read by its id with get_strategy; an account without strategies gets an empty list. An empty symbols list means any pair, so run_backtest then needs symbol. Needs an API key (without one the call is refused with 401) and spends 1 read unit of the daily quota; read only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many of the newest strategies to return.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Strategies returned.
`error`	No	Set only on a failed call (isError true): what went wrong.
`strategies`	No	The account's saved strategies, at most limit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum rows returned."New value: +"How many of the newest strategies to return."

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Strategies returned.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Set only on a failed call (isError true): what went wrong.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "strategies": {
+      "description": "The account's saved strategies, at most limit.",
+      "items": {
+        "description": "One strategy.",
+        "properties": {
+          "active": {
+            "description": "Active on the account.",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "created_at": {
+            "description": "Created (RFC 3339).",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "direction": {
+            "description": "all, long or short.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "engines": {
+            "description": "Engines it uses.",
+            "items": {
+              "description": "Engine.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "Strategy id: pass it to run_backtest as strategy_id.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "min_confidence": {
+            "description": "Minimum confidence, percent (1–100).",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "mode": {
+            "description": "Engine mode.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Name.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "symbols": {
+            "description": "Pairs; empty means any (run_backtest then needs symbol).",
+            "items": {
+              "description": "Pair.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": "array"
+          },
+          "updated_at": {
+            "description": "Updated (RFC 3339).",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "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 already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description adds substantial behavior beyond that: API-key requirement with 401 refusal, a cost of 1 read unit of the daily quota, archived strategies counting toward the limit, no paging, and empty-list behavior for accounts without strategies.

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?

The purpose and returned fields are front-loaded, then usage routing, edge cases, and operational cost follow. Despite its length, every sentence conveys actionable information with no repetition of the schema or annotations.

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 authentication, quota cost, result ordering and contents, archived inclusion, limit and paging behavior, empty-list and empty-symbol edge cases, and sibling alternatives. With an output schema present, it does not need to describe return values, so nothing material is missing for correct invocation.

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% and the single limit parameter is documented in the schema, so baseline is 3. The description adds real meaning beyond the schema by explaining the no-paging behavior and how limits interact with archived strategies, which helps the agent reason about the value and its consequences.

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 the saved strategies on the API key's account'), plus scope details: newest first, archived included, and the returned fields. It distinguishes itself from siblings by naming get_my_bots for live bots and get_strategy for individual lookups, so an agent can route correctly without opening schemas.

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?

Explicitly says to use it to obtain the strategy_id consumed by run_backtest, update_strategy and delete_strategy, and names get_my_bots as the alternative for live bot activity. It also covers the no-paging case by directing the agent to get_strategy by id for strategies beyond the newest limit, and notes the empty-symbols consequence for run_backtest.

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?