Skip to main content
Glama

What can be backtested

describe_data
Read-only

Start here to backtest a trading idea. This server holds the price history (US stocks and ETFs, FX, spot gold and silver, spot crypto; daily and intraday bars) and runs backtests on it. Returns the markets and bar sizes served, the default costs per market, the rules and daily limits every run is held to, and how to write the strategy code; then call create_study.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
notesNo
rulesNo
reasonNo
statusNo
accountNo
marketsNo
messageNo
docs_urlNo
timeframesNo
code_contractNo
default_costsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / account / properties / left_today / properties / per_day
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "engine_seconds": {
      +      "type": "integer"
      +    },
      +    "runs": {
      +      "type": "integer"
      +    },
      +    "studies": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "studies",
      +    "runs",
      +    "engine_seconds"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / default_costs
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "basis": {
      +      "type": "string"
      +    },
      +    "rows": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "commission": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "amount": {
      +                "type": "number"
      +              },
      +              "basis": {
      +                "const": "round_trip",
      +                "type": "string"
      +              },
      +              "fraction": {
      +                "type": "number"
      +              },
      +              "unit": {
      +                "const": "bps",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "amount",
      +              "unit",
      +              "basis",
      +              "fraction"
      +            ],
      +            "type": "object"
      +          },
      +          "example_symbol": {
      +            "type": "string"
      +          },
      +          "market": {
      +            "type": "string"
      +          },
      +          "round_trip_bps": {
      +            "type": "number"
      +          },
      +          "round_trip_pips": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "pair": {
      +                "type": "string"
      +              },
      +              "pips": {
      +                "type": "number"
      +              },
      +              "rate": {
      +                "type": "number"
      +              }
      +            },
      +            "required": [
      +              "pair",
      +              "rate",
      +              "pips"
      +            ],
      +            "type": "object"
      +          },
      +          "slippage": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "amount": {
      +                "type": "number"
      +              },
      +              "basis": {
      +                "const": "per_side",
      +                "type": "string"
      +              },
      +              "fraction": {
      +                "type": "number"
      +              },
      +              "unit": {
      +                "const": "bps",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "amount",
      +              "unit",
      +              "basis",
      +              "fraction"
      +            ],
      +            "type": "object"
      +          },
      +          "timeframes": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "market",
      +          "example_symbol",
      +          "timeframes",
      +          "commission",
      +          "slippage",
      +          "round_trip_bps"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "rows",
      +    "basis"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / docs_url
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds useful behavioral context beyond that: the data universe it serves, that default per-market costs and per-run rules/daily limits are disclosed, and that strategy-code conventions are included. However, much of the 'what it returns' sentence overlaps with the existing output schema, so the net behavioral addition is moderate rather than rich.

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 call to action and the routing instruction is placed at the end where it belongs. The middle sentence is dense — a semicolon-separated inventory of markets and a four-item list of return contents — but each element is informative rather than filler.

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?

For a zero-parameter, read-only discovery tool with an output schema and annotations already present, the description supplies exactly what is missing: what the server covers, what the response will contain, and which sibling to call next. An agent has everything needed to invoke it correctly.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to compensate for. Nothing in the text misrepresents the input surface.

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 action ('Start here to backtest a trading idea') plus the concrete scope of the server's data (US stocks/ETFs, FX, spot gold and silver, spot crypto; daily and intraday bars). It also enumerates what the response contains, so an agent can distinguish this discovery tool from create_study, run_backtest, or get_result without opening any schema.

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?

Gives an explicit entry point ('Start here') and an explicit next step ('then call create_study'), which names the sibling alternative and the condition that selects it. The ordering of the workflow is unambiguous, leaving nothing for the agent to infer.

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