BotSpot: AI Trading, Backtests and Bots

Set required environment variables for a strategy revision

set_runtime_secret_requirements

DestructiveIdempotent

Sets or clears structured runtime secret requirements for an owned strategy revision. Use this when the strategy code needs non-broker API keys or settings, such as AP_API_KEY. This metadata is checked before starting or updating a bot so missing saved variables are caught before deployment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "revisionId": "<revisionId>",
      "runtimeSecretRequirements": "<runtimeSecretRequirements>"
    },
    "name": "set_runtime_secret_requirements"
  }
}

Input Schema

Name	Required	Description
`revisionId`	Yes	AiStrategyRevision.id to update
`strategyId`	No	Strategy.id for ownership resolution
`aiStrategyId`	No	AiStrategy.id for ownership resolution
`runtimeSecretRequirements`	Yes	Structured runtime secret requirements for this revision, or null to clear. Use {version:1, requirements:[{label, description, requiredFor:['deploy'], allOf:[{key,title,description}], anyOf:[...]}]}. Use allOf for keys that are all required and anyOf when one key from a group is sufficient.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare idempotent, destructive, and open-world behavior, so the description's job is additive context. It does add meaningful behavior: setting or clearing replaces prior metadata, and the value is validated before starting or updating a bot so missing variables surface before deployment. It does not restate the destructive/replace semantics beyond 'clears', nor mention ownership-check failures.

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 short sentences, front-loaded with purpose, then usage trigger, then downstream consequence. No filler or restatement of the name; each sentence adds information an agent needs.

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?

With four params, full schema coverage, and rich annotations but no output schema, the description covers what the tool does, when to call it, and what happens downstream. Ownership resolution parameters and the return value are left entirely to the schema, which is acceptable given the coverage.

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% and the runtimeSecretRequirements parameter already documents the version/requirements/allOf/anyOf structure in the schema itself. The description adds no syntax or format detail and says nothing about the optional ownership-resolution parameters, so it stays at the baseline for schema-documented params.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (sets or clears) and a precise resource (structured runtime secret requirements for an owned strategy revision). An agent can distinguish it from set_strategy_requirements by the 'runtime secret' scoping, though the description never explicitly contrasts the two siblings.

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?

Gives a clear trigger: 'Use this when the strategy code needs non-broker API keys or settings, such as AP_API_KEY.' It also explains the deployment-time consequence, which implicitly scopes when the call matters. No explicit when-not or named alternative tool is provided.

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.