Skip to main content
Glama

List strategy-builder options

acubic_list_strategy_options
Read-onlyIdempotent

Lists every choice the strategy builder offers, with ids, trade-offs and defaults: universe, filter metrics, include lists, ranking methods, weighting methods, rebalance, backtest settings and recipes. Optionally one section. It describes options; the choice is the person's. For ready presets use acubic_list_strategy_templates.

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_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
sectionNoOne section, or all (always concise).all
experienceNoKeep only the options available at this experience level.
response_formatNoconcise

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 closed-world, and the description does not merely restate them. It adds useful behavior beyond them: results include ids, trade-offs and defaults, and requesting all sections is "always concise," which sets expectations about payload size. The explicit "the choice is the person's" framing is a real behavioral constraint for an agent that might otherwise pick options.

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?

Front-loaded with the verb and the payload contents, followed by the critical distractor warning, then the alternative. The enumerated content list overlaps somewhat with the section enum in the schema, but it conveys scope quickly enough to earn its place.

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 an output schema present, the description needn't explain return values, and the safety profile is fully covered by annotations. What remains thin is the handling of the experience and locale parameters and the full section catalog, which an agent must discover from the schema; otherwise the definition is sufficient to call the tool correctly.

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 75%, so the schema already documents most parameters, and the four enums are self-describing. The description reinforces the section parameter ("Optionally one section") and the concise default of response_format, but says nothing about locale or experience, and its content list omits several section values present in the enum (risk_levels, countries, industries, themes, exchanges, currencies, instrument_types, etf_exposures, indices).

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?

Uses a specific verb (lists) and resource (strategy-builder options) and enumerates the content domains: universe, filters, ranking, weighting, rebalance, backtest settings, recipes. It explicitly distinguishes itself from acubic_list_strategy_templates, so an agent can route without opening a schema.

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?

Names a concrete alternative ("For ready presets use acubic_list_strategy_templates") and adds a usage stance: "It describes options; the choice is the person's," which tells the agent not to select on the user's behalf. It stops short of stating when not to call this at all, so it falls just shy of full when/when-not 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