Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Optimizer run status and leaderboard

optimization_get
Read-onlyIdempotent

Fetch optimization run status and progress, then return ranked top-N results with robustness scores, guard flags, plateau/Pareto diagnostics, and WFE for strategy assessment.

Instructions

Status and progress; once ranked, the top-N of the leaderboard with robustness scores, guard flags, the plateau and Pareto diagnoses and WFE.

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": {
      "runId": "<runId>"
    },
    "name": "optimization_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
runIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this to be a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful behavioral detail beyond annotations by describing what is returned, including the conditional 'once ranked' state and the specific leaderboard diagnostics. It still does not describe status values, progress semantics, or behavior when a run is not yet ranked.

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 definition is a single dense sentence that front-loads the core status/progress behavior before listing returned artifacts. It is appropriately sized and contains no filler. The string of jargon such as 'plateau and Pareto diagnoses and WFE' is compact but slightly opaque, keeping it from a 5.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only tool with no output schema, the description does a reasonable job listing key returned fields. However, it leaves notable gaps: it does not explain the required runId, the default or bounds of 'top', the possible status/progress values, or what happens before ranking. Completeness is adequate but not strong.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 the burden of explaining parameter meaning. It implicitly clarifies the optional 'top' parameter through 'top-N of the leaderboard', but never mentions the required 'runId' parameter or explains its role, defaults, or constraints. That leaves one of two parameters effectively undocumented in both the 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 clearly states that this tool returns optimizer run status and progress, and once ranked, a leaderboard with robustness scores, guard flags, plateau/Pareto diagnoses, and WFE. The verb is implicit in the tool name, but the resource and returned content are specific. It does not explicitly distinguish itself from siblings like backtest_get or campaign_status, which is why it falls short of a 5.

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: checking progress and retrieving ranked results after an optimization run. The phrase 'once ranked' gives some timing context, but there is no explicit guidance on when to use this tool versus alternatives such as optimization_promote or campaign_status. No exclusions or alternative-routing instructions are provided.

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