Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Research job status and report

research_job_get
Read-onlyIdempotent

Check a research job's status and progress, then retrieve the completed run's ScanSummary—matching research_scan results—once the job is DONE.

Instructions

Status and progress; once DONE, the same ScanSummary as research_scan for the run the job finished into.

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": {
      "jobId": "<jobId>"
    },
    "name": "research_job_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine value by stating the response shape changes with state and that the DONE payload is the same ScanSummary as research_scan — important since there is no output schema. It still omits the set of possible states, whether progress is a percentage, and what happens when the job is missing or failed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, no padding, and the state behavior is front-loaded. However the sentence is telegraphic to the point of ambiguity — the trailing clause about 'the run the job finished into' reads as a fragment and slows comprehension rather than saving space.

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

Completeness2/5

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

With no output schema and 0% parameter coverage, the description carries most of the burden and only explains the DONE case by pointing at another tool's return type. An agent still lacks the non-DONE states, the meaning of `top`, and failure semantics — significant gaps for a two-parameter polling tool.

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% for two parameters, and the description mentions neither. jobId is inferable from context, but `top` (default 10, max 25) is completely unexplained — an agent cannot tell what it limits or which part of the response it affects. The description does not compensate for the coverage gap.

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 identifies the resource (a research job) and what is returned (status and progress, then a ScanSummary once DONE), which is enough to distinguish it from research_scan and research_job_create by name. The phrasing is elliptical — 'for the run the job finished into' is awkward and the verb is implied rather than stated — so it stops short of a clean 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?

Use is implied as polling a job's state, and the 'once DONE' clause hints at the terminal-state check loop. There is no explicit guidance on when to poll this versus the sibling `wait` tool, no polling cadence, and no mention of what to do on failure or unknown jobId.

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