Skip to main content
Glama
bitbank-lab-mcp

bitbank-lab-mcp

Official
by bitbankinc

get_tickers_jpy

Fetches ticker data for all JPY trading pairs and ranks results by 24-hour price change, volume, or pair name to support market overviews and active-pair discovery.

Instructions

[All Tickers / Market Overview] 全JPYペアのティッカー一覧(tickers / ranking / market overview)を取得。変化率・出来高でランキング表示可能。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_tickers_jpy"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
orderNodesc
sortByNochange24h
includeRankedNodata.items はどちらでも、対応ペアに絞ったあとの全件。true(既定): sortBy / order / limit で並べた上位を本文と data.ranked に出す。false: data.ranked を返さず、本文は絞ったあとのペア数と、API 順の先頭 5 件だけ(sortBy / order / limit は使わない)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / includeRanked
      Added value: +{
      +  "default": true,
      +  "description": "data.items はどちらでも、対応ペアに絞ったあとの全件。true(既定): sortBy / order / limit で並べた上位を本文と data.ranked に出す。false: data.ranked を返さず、本文は絞ったあとのペア数と、API 順の先頭 5 件だけ(sortBy / order / limit は使わない)",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / view
      Removed value: -{
      -  "default": "ranked",
      -  "enum": [
      -    "items",
      -    "ranked"
      -  ],
      -  "type": "string"
      -}
  2. Changed1 schema field changedv0.4.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It establishes the read-only, whole-market nature and the JPY-pair scope, but says nothing about result volume, the 50-item cap, default ordering, or how includeRanked changes what comes back. For a read-only listing tool the risk is low, but the behavioral picture remains partial.

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 sentences with the scope tag front-loaded and the ranking capability immediately after. No filler, though the parenthetical 'tickers / ranking / market overview' is somewhat redundant with the rest of the sentence.

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 and four parameters, the description should say more about the shape of the response — particularly the ranked-versus-unranked distinction that includeRanked controls. It conveys enough to pick the tool for a market overview but not enough to predict the payload.

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 only 25% — just includeRanked is documented — so the description must compensate. '変化率・出来高でランキング表示可能' explains the intent behind the sortBy enum values change24h and volume, which is genuine added meaning. It does not cover order, limit, or the name sort option, keeping it short of a full pass.

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?

States a specific verb and resource (取得 of 全JPYペアのティッカー一覧) plus the bracketed scope tag [All Tickers / Market Overview]. The 'all JPY pairs' framing implicitly separates it from the singular get_ticker sibling, though no sibling is named 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?

The description implies usage through 'ranking / market overview' and '変化率・出来高でランキング表示可能', giving a hint of when to reach for it (broad market scanning rather than a single pair). It never states when not to use it or explicitly points to get_ticker for single-pair lookups, so the routing 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.