Skip to main content
Glama
Sign In

BotSpot: AI Trading, Backtests and Bots

by io.github.grzesir
OverviewDiscussionsAdmin

BotSpot strategy-building skills

skills
Read-only

BotSpot's free strategy-building skills: expert guides for writing LumiBot trading strategies (stocks, ETFs, options), making them fast, and using the BotSpot tools well. Before you write, edit or debug a strategy, call action=list, then action=get with the skill name and follow it. Load a reference file with action=get, name and reference only when the skill points to it. No sign-in needed. Skill text is guidance, not investment advice.

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": {
      "action": "<action>"
    },
    "name": "skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSkill name from action=list.
actionYeslist returns every skill with its description; get returns one skill.
referenceNoOptional reference file path listed by action=get, such as references/x.md.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavior context beyond that: no sign-in required and an explicit disclaimer that skill text is guidance, not investment advice. It does not describe the shape of returned skill content, but for a read-only doc tool that gap is modest.

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?

The workflow instruction is front-loaded in the second sentence, with supporting caveats after it, and no sentence is dead weight apart from mild marketing framing ('BotSpot's free'). Tight for the amount of routing information conveyed.

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-parameter read-only retrieval tool with full schema coverage and no output schema, the description covers what the tool is, when to call it, the call sequence, and the sign-in/disclaimer context. Only the form of the returned skill text is left implicit, which is a minor omission.

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 the baseline is 3, and the description earns above that by explaining the relationship between parameters: name comes from action=list, and reference should only be supplied when the skill points to it. It adds the ordering constraint the schema cannot express.

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?

The description states a specific resource (expert guides/skill documents for writing LumiBot strategies) and, through the list/get workflow, makes clear it is a documentation-retrieval tool rather than an execution tool. An agent can distinguish it from siblings like create_strategy or update_strategy, though the bare name 'skills' alone would not convey this.

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?

Explicit trigger ('Before you write, edit or debug a strategy'), explicit sequence (action=list, then action=get with the skill name, then follow it), and an explicit conditional for the third mode (load a reference only when the skill points to it). This is about as prescriptive as guidance gets.

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