Skip to main content
Glama

List my strategies

acubic_list_strategies
Read-onlyIdempotent

Lists the signed-in person's saved strategies, newest first: name, kind (draft, paper or live), holdings count, method, backtest date and link; mode archived shows the archive. It has no performance figures: use acubic_get_strategy for one strategy, acubic_get_backtest for results.

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

Input Schema

NameRequiredDescriptionDefault
modeNoKind of strategy. archived: deleted and still restorable.any
limitNoPage size.
cursorNoA previous next_cursor.
localeNoThe language of this conversation.
name_containsNoCase-insensitive part of the name.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
errorNo
totalNo
truncatedNo
strategiesNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: results are ordered newest first, the exact field set returned, and that archived entries are deleted-but-restorable rather than gone. Return-value format details are left to the output schema.

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 tight sentences with zero filler; the scope and field list come first and the disambiguation/alternatives follow. Every clause carries 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 annotations, an output schema and high schema coverage, the definition covers what an agent needs: scope, ordering, returned fields, and where to go for performance data. Minor remaining gap is no mention of pagination behavior via limit/cursor, which the schema covers alone.

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 description coverage is 83%, so parameters are largely self-documenting and a 3 is the baseline. The description only elaborates on the archived mode and otherwise adds no meaning beyond what the schema states for mode, limit, cursor, locale, name_contains and 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?

States a specific verb and resource ('Lists the signed-in person's saved strategies, newest first') and enumerates the returned fields (name, kind, holdings count, method, backtest date, link). It also names the siblings that cover adjacent purposes (acubic_get_strategy, acubic_get_backtest), so an agent can separate it from them without opening schemas.

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?

Explicitly scopes what this tool does not deliver ('It has no performance figures') and routes to the correct alternative for single-strategy detail and backtest results. The archived-mode note clarifies when that mode applies. It stops short of a full when-not statement for the other list tools, but the guidance given is concrete.

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