Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Backtest RunSummary

backtest_get
Read-onlyIdempotent

Retrieve a finished backtest's stored metrics, exit reasons, layer blocking details, risk events, inert features and re-run verification; reruns server-side, so call sequentially.

Instructions

The RunSummary of a finished backtest: the stored headline metrics (equal to GET /backtests/{id}), exits by reason, per-layer fired/opened/blockedBy with the top blocking conditions, risk events, inertFeatures and re-run verification. Re-runs the backtest server-side, so it takes seconds. Engine-backed: at most 2 such re-runs per user at a time — call these one after another, not in parallel.

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": {
      "backtestId": "<backtestId>"
    },
    "name": "backtest_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
backtestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, but the description adds real operational context beyond them: it re-runs the backtest server-side, takes seconds, and is throttled to at most 2 concurrent re-runs per user. That throttle-and-latency disclosure is exactly the kind of behavior an agent needs to sequence calls correctly. Minor gap: it does not clarify whether a re-run has side effects (cost/quota) despite readOnlyHint=true.

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?

Dense but front-loaded: the return payload is described first, then the cost/concurrency caveat, so the most decision-relevant facts come early. The colon-and-list structure is efficient; the only redundancy is restating 're-runs the backtest server-side' in both the payload list and the operational sentence.

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?

There is no output schema, so the description must carry return semantics, and it does so by naming the RunSummary fields an agent would act on. Combined with the latency and concurrency limits, an agent has enough to call this correctly; the remaining gap is error/precondition behavior for non-finished or unknown backtest IDs.

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 0% for the single backtestId parameter, so the schema contributes nothing but a positive-integer constraint. The description compensates only partially, implicitly signalling that the ID must reference a completed run ('finished backtest') rather than an in-progress one; it never states where that ID comes from or what happens for an unknown/finished-with-errors ID.

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?

States a specific verb and resource: returns the RunSummary of a finished backtest, and enumerates what that summary contains (headline metrics, exits by reason, per-layer counts, risk events, inertFeatures, verification). An agent can tell this is a result-inspection tool rather than a run starter, though it never names a sibling it replaces (e.g. backtest_run).

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 implied rather than stated: the tool applies to a 'finished' backtest, and the last sentence gives a concurrency rule ('call these one after another, not in parallel'). There is no explicit guidance on when to call this versus backtest_run or optimization_get, nor any statement of what to do if the backtest is not yet finished.

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