Skip to main content
Glama
Sign In

BotSpot: AI Trading, Backtests and Bots

by io.github.grzesir
OverviewDiscussionsAdmin

Delete a strategy (soft delete)

delete_strategy
DestructiveIdempotent

Soft-deletes a strategy so it no longer appears in lists or can be used for backtests. Data is preserved in the database for compliance. Two-phase operation: call without confirm (or confirm=false) to preview what will be affected. Call with confirm=true to execute the deletion. Refuses if the strategy has active deployments (stop them first).

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": "delete_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true to actually delete. Default false returns a preview of what will be affected.
strategyIdNoThe Strategy entity ID
aiStrategyIdNoThe AiStrategy entity ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds material context beyond them: the delete is soft, data is preserved for compliance, execution is two-phase, and the call can be blocked by active deployments. It stops short of describing what the preview payload contains or what an error/refusal looks like.

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?

Four sentences, front-loaded with the soft-delete semantics before the two-phase mechanics and the precondition. No filler; each sentence carries distinct operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, annotation-covered mutation with no output schema, this covers safety, reversibility, sequencing, and preconditions well. The remaining gap is identifier selection (Strategy vs AiStrategy ID) and the shape of the preview response, neither of which is resolved anywhere in the definition.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents confirm and the two ID fields; the description's explanation of confirm largely restates the schema. It adds no guidance on the strategyId vs aiStrategyId distinction, which matters because zero parameters are marked required and an agent must decide which identifier to supply.

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 ('Soft-deletes a strategy') plus scope consequences ('no longer appears in lists or can be used for backtests'), which immediately separates it from sibling tools such as clone_strategy, update_strategy, or delete_file.

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 guidance for both modes: call without confirm (or confirm=false) to preview, call with confirm=true to execute. It also states a when-not condition: the call refuses if the strategy has active deployments, and tells the agent to stop them first.

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