Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Save a strategy

strategy_save
Destructive

Creates a crypto trading strategy or saves a new revision so dry-runs and backtests have a saved strategy ID; updates only version when the config changes.

Instructions

Creates a strategy (no strategyId) or saves a new revision of an existing one (strategyId). Dry-runs and backtests need a saved strategy id; a PUT only bumps the version when the config structurally changed. name and description replace the stored ones. visibility: a new strategy is PRIVATE unless you pass PUBLIC. An update never changes visibility (that is strategy_set_visibility, on the user's explicit request only); saving into a PUBLIC strategy publishes the new config to every user, so it is refused unless you pass visibility:"PUBLIC" to confirm, and a visibility that differs from the stored one is refused. Nothing is saved when refused.

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": {
      "name": "<name>",
      "config": "<config>"
    },
    "name": "strategy_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
configYes
strategyIdNo
visibilityNoCreate: default PRIVATE. Update: must match the stored visibility when given; required as "PUBLIC" to save into a PUBLIC strategy.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and non-read-only, so the mutation profile is known; the description nonetheless adds real value by disclosing version-bump conditions, create default PRIVATE visibility, that updates never change visibility, that saving into a PUBLIC strategy publishes config to every user, and that refused saves persist nothing. That said, the description largely reinforces what destructiveHint already signals rather than adding unseen behavioral traits.

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, leading with the create-vs-update distinction and the confirmation requirement before the finer versioning and visibility rules. Every clause carries an operational constraint, though the visibility paragraph is long enough that it could be tightened.

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 5-param mutation with no output schema and nested config, the description covers refusal conditions, versioning, and visibility defaults well enough to call it safely. The main gap is that it never says what config should contain, which matters most given the nested object.

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?

With only 20% schema coverage, the description carries most of the param burden and does: strategyId selects mode, name/description replace stored values, and visibility semantics (create default PRIVATE, must match stored, PUBLIC required to confirm) are spelled out beyond the schema line. The config object's expected contents remain unexplained, keeping it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a precise verb+resource and splits the two modes by the presence of strategyId: create (no strategyId) vs. save a new revision (strategyId). This clearly distinguishes it from siblings like strategy_get, strategy_versions, and strategy_validate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It states prerequisites (dry-runs and backtests need a saved strategy id) and explicitly routes visibility changes to strategy_set_visibility on the user's explicit request only. It also explains when a PUT does and does not bump the version, giving the agent a decision rule rather than a bare action.

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