Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Asynchronous research job

research_job_create

Creates a validated research scan job across symbols and time windows, running one engine scan per combination and returning a job ID to poll for results.

Instructions

POST /research/jobs — a scan with validation/crossSymbol, one engine scan per symbol × window. Returns {jobId}; then wait {kind:"RESEARCH_JOB"}.

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": {
      "request": "<request>"
    },
    "name": "research_job_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesResearchScanRequest with validation (docs://research-scan-reference).

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 non-read-only, non-destructive, non-idempotent, closed-world behavior. The description adds real value beyond that: it discloses the asynchronous job model, the returned jobId, and the per-symbol × window scan cost. It does not mention failure modes, validation errors, or whether duplicate submissions create duplicate jobs (relevant given idempotentHint=false).

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 clauses, front-loaded with the endpoint and the core semantics, with zero filler. The telegraphic style (bare braces, '×') is efficient but slightly cryptic for an agent unfamiliar with the domain.

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 correctly states the return shape ({jobId}) and the required follow-up call, which is the key missing piece for an async tool. The nested request object is delegated to a docs reference, which is acceptable given full schema coverage.

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 coverage is 100% and the single 'request' parameter is documented as a ResearchScanRequest with a docs reference, so the schema carries the burden. The description hints at request content (validation/crossSymbol) but adds no field-level meaning beyond that, making the baseline 3 appropriate.

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 endpoint (POST /research/jobs) and the operation (a scan with validation/crossSymbol, one engine scan per symbol × window), and states the return value {jobId}. It is specific about what is created, though it never uses an explicit verb like 'create' and does not contrast itself with the sibling research_scan.

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?

It gives a useful follow-up instruction — wait with {kind:"RESEARCH_JOB"} — which tells the agent what to do after calling. However, it offers no guidance on when to choose this over research_scan, research_draft, or optimization_create, so the selection decision is left to inference.

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