Skip to main content
Glama
io.github.mohammad-abbasi-sh/paribu-mcp

io.github.mohammad-abbasi-sh/paribu-mcp

paribu_get_ticker

Retrieve 24-hour Paribu ticker snapshots for one market or a ranked, filtered list, returning price, change, and volume data to support market analysis.

Instructions

24h ticker snapshot(s) from Paribu. market: one market id, e.g. "btc_tl" (omit for a ranked list of all 266 markets). quote: filter the list to "tl" or "usdt" (ignored when market is given). limit 1..266. sort: "pair_volume" (default), "percentage", "volume", "change" or "last" — descending. Returns last/first/low/high/average price, 24h change and percentage, base volume and pair (quote) volume.

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": "paribu_get_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNopair_volume
limitNo
quoteNo
marketNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: default sort is 'pair_volume', sorting is descending, limit is bounded 1..266, and quote filtering is silently ignored when market is set. It omits any note on rate limits, errors, or freshness beyond the 24h window, which keeps it from a 5.

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

Conciseness5/5

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

Front-loaded with the one-line purpose, then parameter semantics in a compact, scannable block. Every clause carries information; nothing is redundant padding.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes the returned fields. Combined with full parameter coverage, the definition is nearly complete; only operational caveats (rate limits, error behavior) are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 compensate, and it does for all four parameters: a concrete market id example ('btc_tl'), the accepted quote values ('tl'/'usdt'), the limit range 1..266, and the full set of sort keys with the default. This adds substantial meaning the bare schema lacks.

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: '24h ticker snapshot(s) from Paribu', with the scope of a single market vs. a ranked list of all 266 markets. It is clearly a market-data read, distinguishable in kind from orderbook/trades siblings, though it never names an alternative explicitly.

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?

Gives concrete mode-selection guidance: pass 'market' for one market, omit it for a ranked list, and 'quote' is ignored when 'market' is given. It does not say when to prefer this over paribu_get_orderbook or paribu_market_movers, so it stops short of full alternative routing.

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