Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Validate a strategy config

strategy_validate
Read-onlyIdempotent

Validates a declarative crypto strategy config before saving or running it. Returns pass/fail with error codes matching platform API responses, so configs can be fixed prior to backtesting.

Instructions

Runs the platform validator on a strategy config without saving or running it. Returns {ok:true} or {ok:false, errors:[{code, message, path?}]} with the same codes as a 422/400 from POST /strategies. Read docs://strategy-config-reference 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": {
      "config": "<config>"
    },
    "name": "strategy_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesThe strategy config JSON (docs://strategy-config-reference).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and closed-world, so the safety profile is covered. The description goes beyond that by spelling out the exact response envelopes {ok:true} and {ok:false, errors:[{code, message, path?}]}, and by stating the error codes match the 422/400 from POST /strategies — real behavioral context an agent cannot get from the annotations or schema.

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: what it does and its non-effects first, the return contract second, the prerequisite last. No filler, and the most decision-relevant clause ('without saving or running it') is front-loaded.

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

Completeness5/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 carries the return-shape burden and does so precisely, including the conditional error array and its fields. Combined with the doc pointer for the nested config object, an agent has everything needed to call and interpret this tool.

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?

There is a single parameter, config, and schema description coverage is 100%, with the schema already pointing at docs://strategy-config-reference. The description adds no further detail about the config object's nested structure, which is the baseline-3 case where the schema carries the load.

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?

Specific verb and resource: "Runs the platform validator on a strategy config", with the important qualifier "without saving or running it". That distinguishes it from strategy_save and backtest/run paths, but it never explicitly contrasts with the closely-named sibling strategy_dry_run, so the reader 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is clearly implied: validate a config before it is persisted or executed, which is exactly the pre-flight scenario. The instruction "Read docs://strategy-config-reference first" is a concrete prerequisite. It stops short of a 5 because it names no alternative (e.g. when to prefer strategy_dry_run) and states no when-not conditions.

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