Analyzera

Check a backtest

get_backtest_status

Read-onlyIdempotent

Whether a backtest started by run_strategy_backtest is queued, running, done or failed (state), with an ETA while it runs. Free to call. It waits up to 20s for a running backtest to finish before answering, so call it again rather than sleeping between calls.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "get_backtest_status"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes

Output Schema

Name	Required	Description
`key`	Yes	Pass to get_backtest_status to follow this backtest.
`say`	No	The same status as a sentence.
`step`	No	What the job is doing now.
`error`	No
`notes`	No	Rebalance dates that did not build and what was held instead; the returns include those periods.
`state`	Yes
`started_at`	Yes
`eta_seconds`	No	Seconds until it should be done; None once it is.
`strategy_id`	Yes
`elapsed_seconds`	Yes
`expected_seconds`	Yes	How long a backtest usually takes.
`representative_from`	No	Every rebalance from this date on built as defined; quote returns from it. None when no date was skipped.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds two behaviors the annotations cannot express: the call blocks up to 20s waiting for a running backtest to finish, and it is free to call. Those facts materially change how an agent should poll, which is exactly what this dimension rewards.

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?

Three tight sentences, front-loaded with what the tool returns, followed by cost and the polling caveat. No filler and nothing repeated from annotations or schema.

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 simple status-poll tool with an output schema, this covers the essentials: possible states, ETA availability, cost, and blocking behavior. The only real gap is that the required `key` parameter is left entirely unexplained, which an agent would have to infer from `run_strategy_backtest`.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%: `key` is a bare string with maxLength 128 and no description. The description never mentions `key`, its expected format, whether it is the id returned by `run_strategy_backtest`, or how long it remains valid. With one undocumented required parameter, the description should compensate but does not.

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?

The description names a specific verb and resource and enumerates the exact status values (queued, running, done, failed) that `state` can take. It also ties itself to the sibling that produces the backtest (`run_strategy_backtest`), so an agent can tell the two apart 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?

Usage context is clear: call it on a backtest started by `run_strategy_backtest`. It even gives concrete polling guidance ('call it again rather than sleeping between calls'), which is the main decision the agent faces. There is no explicit 'do not use when…' exclusion, which keeps it just short of 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Analyzera tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?