Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Tradable symbols

market_symbols
Read-onlyIdempotent

Lists tradable symbols with available candle history for a chosen market type and optional exchange, so you can confirm which crypto pairs a backtest can use.

Instructions

Symbols the platform holds candles for, per market type.

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

Input Schema

NameRequiredDescriptionDefault
exchangeNo
marketTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond the annotations: the list is limited to symbols the platform actually holds candles for, not all tradable instruments. It says nothing about result shape, ordering, or size, though.

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 short sentence with no filler, and the key scope ('symbols the platform holds candles for') comes first. It is efficient to the point of being terse, but nothing is wasted.

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, the description should say what a 'symbol' is (a bare ticker string or an object with metadata) and whether the result is filtered or paginated; it does neither. It also leaves the exchange parameter unexplained, which for a two-parameter tool with zero schema coverage is a real gap.

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 parameter meaning, and it only partly does: 'per market type' implies marketType is the filter (the enum in the schema already enumerates spot/futures). The exchange parameter is left entirely undefined in both schema and description, and there is no indication of whether exchange is required in practice or what values it accepts.

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

Purpose3/5

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

The description identifies the resource returned (symbols with candles) and the scoping dimension (market type), which is more specific than the bare title 'Tradable symbols'. However it is a noun phrase with no verb and no differentiation from siblings such as market_coverage, so an agent must infer that this is a listing lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this tool, no prerequisites, and no pointer to any alternative such as market_coverage. The only implicit cue is 'per market type', which hints at the required parameter but not the usage context.

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