Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Compare 2–4 backtests

backtest_compare
Read-onlyIdempotent

Compare up to four backtest runs side by side to see headline metrics, platform comparability warnings, and a structural config diff against the first run.

Instructions

Headline metrics side by side, the platform comparability warnings, and the structural config diff of each run against the first.

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": {
      "backtestIds": "<backtestIds>"
    },
    "name": "backtest_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
backtestIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. Beyond that, the description adds real behavior: what is returned (metrics, platform comparability warnings, config diff) and the important framing that every run is diffed against the first — since there is no output schema, this return-value disclosure is doing meaningful work. It stops short of describing response shape or what happens with incomparable runs.

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?

One sentence, no filler, and it front-loads the primary output (headline metrics) before the secondary artifacts (warnings, config diff). Nothing in the sentence is redundant with the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity read-only tool with one parameter and no output schema, the definition covers the essentials of what comes back and how the comparison is anchored. It leaves out error/edge behavior (invalid or non-comparable IDs) and any sense of result size or structure, which an agent would otherwise need.

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?

Schema coverage is 0%, so the description must compensate for the single undocumented parameter. It does so by establishing that backtestIds is an ordered list where the first element is the comparison baseline — a semantic the schema (array of ints, 2–4 items) does not convey and which materially affects how the caller orders the IDs.

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 names the resource (backtests) and what comparison produces — headline metrics side by side, comparability warnings, and a structural config diff — which is specific enough to distinguish it from backtest_get (single run) and the other backtest_* siblings. It is written as a noun phrase with no verb, so the action ('compare') is only inferable from the title, which keeps it from 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 implied rather than stated: an agent can infer this is the tool for comparing several runs, with 'against the first' hinting the first ID is the baseline. There is no explicit 'use this instead of backtest_get' guidance and no preconditions (e.g., whether the runs must share a strategy or config) are given.

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