Skip to main content
Glama

List strategy templates

acubic_list_strategy_templates
Read-onlyIdempotent

Lists the ready preset strategies, one per experience level and risk level (largest accepted drawdown), plus Custom (advanced): the full engine. Each preset gives its universe rules, recommended pair and the arguments for acubic_create_strategy. Use it to explore or compare presets before choosing; single settings and their ids are in acubic_list_strategy_options.

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

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
experienceNoLimit to one experience level.
risk_levelNoOne risk level only (largest accepted drawdown).
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
errorNo
templatesNo
truncatedNo
content_localeNoLanguage of the wording: en for now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive and an output schema exists, so the description's remaining burden is low. It still earns credit for disclosing the shape of the payload (one preset per experience x risk level, plus a Custom 'full engine' entry) and that presets carry pre-built arguments for acubic_create_strategy, which annotations alone do not reveal.

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?

Two sentences, both front-loaded with the resource definition before the alternative-tool pointer. No filler, no repeated annotation content, and the parenthetical glosses ("largest accepted drawdown", "the full engine") are compressed where they need to be.

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?

With annotations covering safety, an output schema covering return shape, and enum-documented parameters, the description only needed to convey the preset-vs-custom model and the hand-off to acubic_create_strategy. It does exactly that, so nothing an agent needs to call this correctly is 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 description coverage is 75% and every parameter is an enum with its own description, so the schema largely documents the inputs. The description adds meaning by explaining that experience and risk level act as partition dimensions ("one per experience level and risk level") and by glossing risk level as largest accepted drawdown, though it says nothing about locale or response_format.

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?

"Lists the ready preset strategies, one per experience level and risk level ... plus Custom" gives a specific verb, resource, and enumeration structure. It also states what each returned item contains (universe rules, recommended pair, arguments for acubic_create_strategy), which is more than a restatement of the name.

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?

"Use it to explore or compare presets before choosing" gives a clear use case, and it routes readers to acubic_list_strategy_options for single settings and ids. What's missing is an explicit statement of when not to use it (e.g. versus acubic_list_strategies for already-created strategies), so it falls just short of full alternative coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources