Skip to main content
Glama

BaseEdge Labs Catalog

List presets

list_presets
Read-onlyIdempotent

The presets served here (the free ones, plus a licensed account's paid ones), each with its instrument, timeframe, a plain description and its Strategy Tester results. Filter by strategy, instrument (for example MNQ, MGC, XAUUSD) or timeframe.

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

Input Schema

NameRequiredDescriptionDefault
strategyNoA strategy_id or name from list_strategies
timeframeNoA chart timeframe, for example 5m
instrumentNoA symbol or part of one, for example MNQ or XAUUSD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value the annotations cannot: it discloses that results are scoped by licence tier (free plus licensed paid presets) and that each record carries Strategy Tester results. Return shape is described at field level, which is helpful given no 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is returned, then the filtering options. Dense but every clause carries information; no filler or restatement of the tool name.

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 read-only, three-optional-filter list tool with no output schema, the description covers payload contents, access scoping and filtering. The only meaningful gap is the absence of guidance about how results relate to the sibling tools, which is a guidance issue rather than a completeness one.

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%, with the schema already supplying the strategy/timeframe/instrument descriptions and the MNQ/XAUUSD examples. The description repeats the same example symbols and adds only the notion that filtering is optional/partial, so it earns the baseline rather than more.

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 uses a specific verb (list) plus resource (presets) and enumerates what each entry contains – instrument, timeframe, description and Strategy Tester results. It also states the access scope (free presets plus a licensed account's paid ones), which goes beyond the title. It does not explicitly contrast itself with the get_preset or list_strategies siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the sentence 'Filter by strategy, instrument ... or timeframe' tells the agent how to narrow results but never says when to call this instead of get_preset (single preset) or list_strategies (available strategies). No exclusions or prerequisites are given.

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