Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Strategy draft from a finding

research_draft
Read-onlyIdempotent

Build a strategy config from a saved finding by coordinates; the server reads stored report numbers and returns config, provenance, run, and limitations to validate and save before backtesting.

Instructions

Builds a strategy config from a saved finding, addressed by coordinates (the server reads the numbers from its stored report). Returns {config, provenance, run, limitations}; validate and save it before running.

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>",
      "kind": "<kind>",
      "horizon": "<horizon>"
    },
    "name": "research_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
runIdYes
sliceNofamily:name, required for SLICE.
targetNo
featureNo
horizonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the bar is lower. The description still adds real value by explaining that the server resolves the numbers from its own stored report rather than trusting caller-supplied values, and by disclosing the return shape. It omits failure behavior, e.g., what happens if the finding is missing or coordinates are stale.

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 compact sentences with the output contract and the required next steps front-loaded. Dense but no sentence is wasted; the parenthetical is a little compressed but earns its place.

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?

With no output schema, the inline return description ({config, provenance, run, limitations}) is genuinely useful, and the pre-run validation requirement is captured. However, for a six-parameter tool with a nested object and near-zero schema coverage, the description leaves too much input semantics unexplained to be considered complete.

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 coverage is only 17% with six parameters, three required, and a nested target object, so the description carries the burden. The 'coordinates' remark hints that values are references, but it never explains runId, kind, horizon, feature, or the target sub-fields, leaving most parameters undocumented in both places.

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?

States a specific verb and resource: 'Builds a strategy config from a saved finding.' That distinguishes it clearly from strategy_save, strategy_validate, and strategy_get, which the description implicitly positions as downstream steps. The phrase 'addressed by coordinates' is slightly cryptic but doesn't obscure what the tool produces.

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?

Gives an explicit workflow ordering: 'validate and save it before running,' which names the relevant sibling steps. It does not say when not to use this tool or what to do if no saved finding exists, but the when-to-use context is clear.

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