Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

List strategy versions

strategy_versions
Read-onlyIdempotent

Retrieve a trading strategy's version history newest first; optionally diff two versions to see which structural paths changed. Use it to audit edits and compare strategy versions.

Instructions

Version history, newest first. With diff:[a,b], also the structural diff of version a → version b (paths that changed).

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": {
      "strategyId": "<strategyId>"
    },
    "name": "strategy_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffNo
strategyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing ordering (newest first) and the shape of the diff result (changed paths), but says nothing about result size, pagination, or what a version entry contains.

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?

Two short sentences, front-loaded with the primary behavior and then the optional diff mode, with no filler. Slightly terse to the point that the leading noun phrase lacks an explicit verb.

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, read-only tool with rich annotations, a two-parameter schema, and no output schema, this is nearly complete: ordering and the diff return content are both covered. The main residual gap is the unexplained required strategyId and any indication of result volume.

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 must carry parameter meaning. It does explain the diff parameter well — a two-element [a,b] array yielding the structural diff from version a to version b with the paths that changed — but strategyId, the required parameter, is left entirely unexplained by both schema and description.

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 states a specific resource and behavior — version history, ordered newest first — which is clearly distinct from strategy_get (single strategy) or strategy_save (mutation). The verb is implied rather than explicit ("Version history"), and no sibling is named, but the intent is unambiguous.

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: an agent can infer it should call this when it needs version history or a diff between two versions. There is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives such as strategy_get for a single version's content.

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