Skip to main content
Glama
Sign In

BotSpot: AI Trading, Backtests and Bots

by io.github.grzesir
OverviewDiscussionsAdmin

List all strategies for the authenticated user

list_strategies
Read-onlyIdempotent

Returns all strategies owned by the current user. Each item includes both strategyId and aiStrategyId so you can use either with other tools (delete_strategy, list_revisions, start_backtest, etc.). Optionally filter by name. The name filter is case-insensitive and also returns close word-token matches, so if an exact phrase returns a near miss you should inspect the returned names before saying the strategy does not exist. Use this when the user explicitly names or identifies a strategy, especially when that name differs from the currently open page/context. Trigger phrases include 'the one entitled X', 'apply this to X also', and 'do not change Y'. The explicit named target wins; after resolving it, only read or edit that named strategy unless the user also asks to compare/copy from the open one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_strategies"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilter by name (case-insensitive partial or close word-token match)
limitNoMax results to return (default 50)
offsetNoSkip N results for pagination (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is settled. The description adds non-obvious behavior beyond that: the name filter is case-insensitive and performs close word-token matching, and near-misses should be inspected before concluding a strategy does not exist. It does not mention result ordering, though the schema handles paging defaults.

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?

Purpose and returned fields are front-loaded, and every sentence is on-topic. The final two sentences about which target wins and post-resolution behavior are slightly verbose agent-policy guidance, but they remain useful rather than 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?

For a three-optional-parameter read-only list tool with no output schema, the description covers purpose, filter semantics, returned fields, and downstream usage of the returned IDs. Nothing an agent needs in order to call it correctly appears to be 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 goes beyond the schema by explaining the fuzzy token-matching behavior of the name filter and by explaining that either returned ID can be fed to delete_strategy, list_revisions, or start_backtest. That adds real meaning about how the parameters and results interact with sibling tools.

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?

The first sentence gives a specific verb and resource with an explicit ownership scope ("all strategies owned by the current user"), which separates it from a marketplace/catalog listing. The follow-up sentence clarifies what each item contains (strategyId and aiStrategyId), so the agent immediately knows this is the discovery/resolution entry point.

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?

It states when to use it (user explicitly names or identifies a strategy, especially when the name differs from the open page) and supplies concrete trigger phrases. It also gives exclusions and a post-resolution rule: only read or edit the named strategy unless the user also asks to compare/copy from the open one. That is unusually prescriptive routing guidance.

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

All BotSpot: AI Trading, Backtests and Bots 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