Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Campaign ledger and lock

campaign_status
Read-onlyIdempotent

Retrieve active or named campaign status: locked region, trial count, Sharpe distribution, refusals, finalization. Check if a strategy version is in the ledger and which robustness checks it lacks.

Instructions

The active (or named) campaign: locked region per timeframe, trials (m — the number the DSR is deflated by, inherited trials included), the Sharpe distribution of all attempts, the last rows, refusals, and the finalization once it exists. With strategyId (+ strategyVersion): whether that exact config is in the ledger and which robustness checks it still lacks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "campaign_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdNo
strategyIdNo
strategyVersionNo

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so safety behavior is covered. The description adds genuine domain context (DSR deflation, inherited trials, refusals, finalization state) beyond the annotations, but says nothing about what happens when no campaign exists or how campaignId resolves to the active one, leaving the interface contract partly implicit.

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 sentences, front-loaded with the primary resource, and the parenthetical gloss on 'm' earns its place for a jargon-heavy field. It is dense but not padded; the nested clauses in the first sentence make it slightly harder to scan than it needs to be.

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 effectively substitutes for one by enumerating the ledger fields and the strategy-mode result. Given a read-only tool with three optional parameters and full annotation coverage, the remaining gaps (campaignId semantics, absent-campaign behavior, version defaulting) are modest rather than disqualifying.

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 carries the burden: it explains that strategyId plus strategyVersion triggers a membership/robustness-gap answer, which is real added meaning. However campaignId is only obliquely covered by 'named' campaign, and the description never states whether strategyVersion defaults to the latest version, leaving one of three parameters ambiguous.

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 (the active or named campaign) and enumerates the contents it exposes: locked region per timeframe, trials/m, Sharpe distribution, last rows, refusals, finalization. It also states the alternate mode keyed on strategyId. It is a nominal phrase rather than a verb, and it never says plainly 'returns/reads', but the resource and its scope are unmistakable and clearly distinct from campaign_start/campaign_finalize.

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: calling with no arguments yields the active campaign's ledger, and adding strategyId (+ strategyVersion) switches to a membership/robustness-gap check. There is no explicit guidance on when to prefer this over backtest_get, strategy_get, or campaign_finalize, and no mention of prerequisites such as an existing campaign.

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