Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Backtest trades (one page)

backtest_trades
Read-onlyIdempotent

Retrieve paginated trades from a Janorium backtest, filter by side, exit reason, or entry layer, and inspect entry/exit, PnL, fees, funding, and risk metrics.

Instructions

One page of trades: side, entry/exit time and price, quantity, pnl/pnlPct, fees, fundingPaid (signed: negative was paid), exitReason, rMultiple, maePct/mfePct, barsHeld, entryLayerId and parentPositionId (the slices of one take-profit ladder share it). Omitted to keep rows short: leverage, marginUsed, liquidationPrice, slippageCost, feeKind, sizeFactor, riskAmount — GET /backtests/{id}/trades has them. size ≤ 50; the filter applies within the page.

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_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sizeNo
filterNo
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 read-only, idempotent, non-destructive behavior, so the description's added value is the paging and filtering semantics. It discloses the real gotcha that 'the filter applies within the page' rather than across the full result set, and it names which fields are deliberately omitted and where to retrieve them — both are traits an agent cannot get from the schema or annotations.

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?

The return shape is front-loaded and the long field enumerations earn their place because they define what is and is not returned. The density is high but the sentences are purposeful, with only mild redundancy between the field list and the omitted-fields list.

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?

With no output schema, the description correctly takes on the burden of describing the row shape, the omitted columns, the fallback endpoint, the size cap, and filter scope. What remains unstated is paging depth — how many pages exist or how to know when to stop — which matters for a paginated reader.

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%, so the description has to carry parameter meaning and it only partially does: it documents the size ceiling (≤ 50) and the page-scoped filter behavior, and the listed row fields map loosely to the filter keys (side, exitReason, entryLayerId). It never explains the page parameter, defaults, or whether paging is zero-based, leaving a real gap against the 0% coverage baseline.

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 opening clause 'One page of trades' plus the field inventory makes clear this returns a paginated slice of a backtest's trade rows. The resource is unambiguous, but nothing in the text distinguishes it from siblings such as backtest_get or backtest_compare, so an agent must infer the boundary.

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 only implied: it hints that GET /backtests/{id}/trades is the place to go when the omitted fields are needed, which is a useful alternative for one specific case. There is no explicit statement of when to choose this tool over other backtest tools, nor any prerequisite guidance.

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