Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Candle coverage

market_coverage
Read-onlyIdempotent

Check candle, funding, and futures-metrics coverage per symbol and timeframe to choose a valid backtest period.

Instructions

Per symbol × timeframe: first and last candle, count, hours since the last candle, funding and futures-metrics coverage. Check before choosing a period.

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": {
      "marketType": "<marketType>"
    },
    "name": "market_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNo
exchangeNo
timeframeNo
marketTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real value by disclosing the returned signals (gaps, staleness via hours-since-last-candle, funding/futures-metrics coverage), but says nothing about behavior when a symbol/timeframe has no candles or how the default exchange is resolved.

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?

A single dense sentence, front-loaded with the grouping key and followed by the reported fields and the usage cue, with no filler. The fragment style ('Per symbol × timeframe:') is terse but readable and efficient.

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 description correctly spends its words enumerating return fields. It is still short of complete for a 4-parameter tool with zero schema coverage: the required marketType and the exchange default are unstated, and the caller cannot tell what an empty result means.

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 parameter burden. 'Per symbol × timeframe' explains two of four parameters; it leaves the required marketType (spot vs futures enum) and exchange completely unaddressed, and the required flag on marketType is never surfaced in prose.

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?

Names the resource (candle/market data coverage) and enumerates exactly what is reported: first and last candle, count, hours since last candle, funding and futures-metrics coverage. It is clearly a pre-flight data-availability lookup rather than a data-fetching tool, though it never states the verb 'returns' explicitly.

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?

'Check before choosing a period' gives one clear usage context (validate data span before running a backtest/optimization), which is genuinely actionable. However it names no alternative tool and gives no when-not guidance, e.g. what to do if coverage is insufficient or whether a sibling such as market_symbols should come first.

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