Skip to main content
Glama

Read a result

get_result
Read-only

Reads a backtest result by its run_id (when run_backtest answered "running", call this until the run ends), or a study's runs by study_id (one of them with version). A run comes with its trades, a page at a time (trades_page).

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

Input Schema

NameRequiredDescriptionDefault
run_idNoA run_id run_backtest or run_held_out_test returned.
versionNo
study_idNoA study's id, for its runs (the newest 20 by default); with `version`, one of them.
trades_pageNoWith a run (run_id, or study_id with version): the page of its trade list, from 1; a page holds 100 trades. Left out: the first.
before_versionNoWith study_id: the 20 runs before this version (a list's `next` gives it).

Output Schema

NameRequiredDescriptionDefault
nextNo
runsNo
basisNo
gradeNo
linesNo
marketNo
reasonNo
run_idNo
statusYes
windowNo
messageNo
metricsNo
noticesNo
versionNo
headlineNo
held_outNo
hold_outNo
settingsNo
study_idNo
warningsNo
retryableNo
cost_tableNoEvery cost the run charged: each component (commission, slippage, spread) with its amount, unit and basis, what it comes to per round trip, when it is taken, and whether it is yours (caller) or the market's default; the round trip summed by unit (pips on a currency pair, the costs stated in pips). Costs you send replace the market's defaults side by side: a commission replaces the default commission, a slippage or a spread replaces the default slippage, a side you leave out is charged at the market's default, and nothing is added on top.
disclaimerNoThe hypothetical-performance line, on a result (a run, or a study's runs): the same text the app shows with every result.
look_aheadNo
trade_listNoThe run's trades in the order they were made, a page at a time: when each entered and left (a day on daily bars; a time on the `clock` on shorter ones; "open at the end" for a trade still open when the data ended), its side, whether it won or lost after costs, and which exit ended it (a word: stop, exit rule, target, time limit…). No prices, levels, sizes or returns.
buy_and_holdNo
replayed_fromNo
grade_withheldNo
runs_left_todayNo
hold_out_estimateNo
poll_after_secondsNo
stated_rule_breaksNo
highest_simulated_valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / cost_table / properties / components / items / properties / unit / enum
      Previous value: -[
      -  "percent",
      -  "bps",
      -  "usd_per_share",
      -  "usd_per_ounce",
      -  "pips",
      -  "usd_per_order"
      -]New value: +[
      +  "percent",
      +  "bps",
      +  "usd_per_share",
      +  "usd_per_ounce",
      +  "pips",
      +  "usd_per_order",
      +  "usd_per_lot"
      +]
    • addedOutput schema / properties / settings / properties / costs_charged / properties / value / items / properties / lot_ounces
      Added value: +{
      +  "type": "number"
      +}
    • changedOutput schema / properties / settings / properties / costs_charged / properties / value / items / properties / unit / enum
      Previous value: -[
      -  "percent",
      -  "bps",
      -  "usd_per_share",
      -  "usd_per_ounce",
      -  "pips",
      -  "usd_per_order"
      -]New value: +[
      +  "percent",
      +  "bps",
      +  "usd_per_share",
      +  "usd_per_ounce",
      +  "pips",
      +  "usd_per_order",
      +  "usd_per_lot"
      +]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / cost_table
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Every cost the run charged: each component (commission, slippage, spread) with its amount, unit and basis, what it comes to per round trip, when it is taken, and whether it is yours (caller) or the market's default; the round trip summed by unit (pips on a currency pair, the costs stated in pips). Costs you send replace the market's defaults side by side: a commission replaces the default commission, a slippage or a spread replaces the default slippage, a side you leave out is charged at the market's default, and nothing is added on top.",
      +  "properties": {
      +    "components": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "amount": {
      +            "type": "number"
      +          },
      +          "basis": {
      +            "enum": [
      +              "per_side",
      +              "round_trip"
      +            ],
      +            "type": "string"
      +          },
      +          "charged": {
      +            "description": "When and on what the engine takes it.",
      +            "type": "string"
      +          },
      +          "component": {
      +            "enum": [
      +              "commission",
      +              "slippage",
      +              "spread"
      +            ],
      +            "type": "string"
      +          },
      +          "origin": {
      +            "description": "caller: your costs; default: the market's default.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "per_round_trip": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "amount": {
      +                "type": "number"
      +              },
      +              "unit": {
      +                "enum": [
      +                  "bps",
      +                  "pips",
      +                  "usd",
      +                  "usd_per_share",
      +                  "usd_per_ounce"
      +                ],
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "amount",
      +              "unit"
      +            ],
      +            "type": "object"
      +          },
      +          "unit": {
      +            "enum": [
      +              "percent",
      +              "bps",
      +              "usd_per_share",
      +              "usd_per_ounce",
      +              "pips",
      +              "usd_per_order"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "component",
      +          "amount",
      +          "unit",
      +          "basis",
      +          "per_round_trip",
      +          "charged",
      +          "origin"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "defaults_replaced": {
      +      "description": "The market defaults your costs replaced: none of them was charged, and nothing was added to your costs.",
      +      "items": {
      +        "enum": [
      +          "commission",
      +          "slippage"
      +        ],
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "round_trip_total": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "bps_of_value": {
      +          "type": "number"
      +        },
      +        "pips": {
      +          "type": "number"
      +        },
      +        "usd": {
      +          "type": "number"
      +        },
      +        "usd_per_ounce": {
      +          "type": "number"
      +        },
      +        "usd_per_share": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "bps_of_value"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "components",
      +    "defaults_replaced",
      +    "round_trip_total"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / market / properties / derived_only / description
      Added value: +"True when the market-data licence lets the account see only results derived from the prices (figures, never the prices or bars themselves). It says what may be shown, not how the quote is made."
    • addedOutput schema / properties / window / properties / gaps
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "from": {
      +        "type": "string"
      +      },
      +      "to": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "from",
      +      "to"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. First observed

TDQS

A3.6/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. The description adds the useful behavioral detail that results are polled until a run ends and that trades come back paginated, but it says nothing about volume, truncation, or what happens on an unknown run_id. With annotations doing the heavy lifting, this is adequate but not 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?

It is a single front-loaded sentence with no filler, and the primary 'read a result' purpose comes first. The nested parentheticals make it slightly dense, but every clause carries operational meaning.

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?

An output schema exists, so return values need not be explained, and the description covers the main run_id and study_id paths plus trade pagination. It omits before_version list navigation, but the schema documents that parameter, leaving no critical gap for correct invocation.

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 80%, so the schema already explains run_id provenance, study_id's default of the newest 20 runs, version pairing, and the 100-trades-per-page rule. The description restates the run_id/study_id split and adds the polling intent, but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 ('Reads') and names the resource precisely, and it splits the tool into two clear modes: a run by run_id, or a study's runs by study_id. It ties the tool to the producing sibling run_backtest, but does not position it against other read-side alternatives such as compare_trades.

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?

It gives explicit situational guidance, notably that this is the polling tool to call repeatedly while run_backtest reports 'running', and that supplying version with study_id selects a single run. There is no explicit 'when not to use' or exclusion statement, which keeps it short of a 5.

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