BotSpot: AI Trading, Backtests and Bots

Remove a strategy from the marketplace

unpublish_from_marketplace

DestructiveIdempotent

Removes a strategy from the public marketplace. The strategy becomes private and is no longer discoverable by other users. Existing private share links (if any) are NOT affected. Uses soft-delete (sets isActive=false). Accepts the marketplace listing ID, or a strategy/aiStrategy ID to find the listing automatically.

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

Input Schema

Name	Required	Description
`listingId`	No	The marketplace listing ID (fastest lookup)
`strategyId`	No	The Strategy entity ID (alternative)
`aiStrategyId`	No	The AiStrategy entity ID (alternative)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructive and idempotent, but the description adds the substantive mechanics: soft-delete via isActive=false, the strategy drops out of public discovery, and existing private share links survive untouched. That is precisely the blast-radius information an agent needs before a destructive call, and none of it is in the structured fields.

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 short sentences, front-loaded with the action and its effect, then the important non-effect on share links, then the implementation note, then the input alternatives. No sentence is filler and each adds a distinct fact.

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 three-param destructive tool with no output schema, the description covers effect, persistence model, and ID resolution well. It leaves out failure behavior when no listing is found and does not explicitly state that at least one of the three IDs must be supplied, which matters given required=[] in the schema.

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 each parameter is already documented as 'fastest lookup' or 'alternative'. The description restates that they are interchangeable lookup keys and implies only one is needed, but adds no format, precedence, or conflict-resolution detail beyond the schema.

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 ('Removes a strategy from the public marketplace') and immediately constrains scope by explaining the strategy becomes private rather than deleted. That phrasing makes it distinguishable from delete_strategy and other lifecycle siblings without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the three mutually-exclusive lookup paths (listing ID as fastest, or a strategy/aiStrategy ID to auto-resolve the listing), which is real guidance for invocation. It stops short of stating when-not to use it (e.g. versus delete_strategy or removing a plan item), and the schema shows zero required params, so the 'at least one ID' rule is only implied.

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 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.