Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Synchronous research scan

research_scan

Run a scan to evaluate crypto trading strategy hypotheses and return hypothesis/admission counts, top findings, clusters, and caveats.

Instructions

POST /research/scan with a body per docs://research-scan-reference. Returns a ScanSummary: hypothesis counts (always quote them with any finding), admission counts, top findings with netDecileSpread, clusters, caveats. Bodies with validation or crossSymbol must use research_job_create. Inside a campaign its hypotheses count as trials.

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_scan"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/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, so the safety profile is covered. The description adds real behavioral context beyond that: the response shape, the instruction to always quote hypothesis counts with any finding, and the side effect that hypotheses inside a campaign count as trials. It loses a point for deferring the actual body contract to an external docs:// reference.

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?

Front-loaded with the endpoint and return type, then the qualification rules, with no filler sentences. It is dense and jargon-heavy (netDecileSpread, admission counts), but every clause carries operational information.

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?

No output schema exists, and the description compensates by naming the ScanSummary fields, which is the right call. It omits latency/blocking expectations (the word 'Synchronous' appears only in the title) and any cost or rate-limit note, which matter for a non-idempotent compute call.

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%, so the baseline is 3, and the description adds no field-level meaning beyond what the schema says. Both the schema and the description simply point to docs://research-scan-reference, leaving the single request object opaque either way.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action (POST /research/scan returning a ScanSummary) and enumerates the return contents, so an agent knows exactly what it gets. It also distinguishes itself from the sibling research_job_create by naming the body shapes that must go there instead.

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?

Provides an explicit routing rule: bodies containing validation or crossSymbol must use research_job_create. That is a concrete when-to-use-an-alternative condition, though there is no broader guidance on when a scan is preferable to research_draft or a full campaign, so it stops short of full coverage.

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