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

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

paribu_list_markets

List Paribu market pairs with base/quote assets, price and amount precision, labels, and OTC-only flags. Filter by quote currency like TL or USDT to narrow results.

Instructions

The full Paribu market catalogue from the exchange config: 467 pairs with base/quote, price and amount precision and steps, labels and the OTC-only flag. quote: filter to "tl" or "usdt" (omit for all). limit 1..467.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
quoteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the data source (exchange config) and the catalogue size (467 pairs), implying a static reference read, but says nothing about whether results are cached, whether the call hits the network, or how limit interacts with the total catalogue.

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?

Three short lines, front-loaded with the resource and its payload, then the two parameter constraints. The "quote:" line is slightly telegraphic but nothing is wasted.

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?

An output schema exists, so return shape needn't be described, and both parameters get coverage. The gap is that the default limit of 50 silently truncates a 467-pair catalogue with no offset parameter, and the description's "full catalogue" framing does not warn an agent to raise limit to get everything.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the quote parameter is an unconstrained string/null in the schema, so the description does real work by supplying the valid values "tl" and "usdt" and the omit-for-all semantics. It also bounds limit to 1..467, though it omits the schema's default of 50.

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 (list the market catalogue) and enumerates what each entry carries: base/quote, price and amount precision and steps, labels, and the OTC-only flag. The subject matter is clearly distinct from price/orderbook/ticker siblings, 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?

It gives filtering guidance for the quote parameter ("tl" or "usdt", omit for all) and a limit range, which is useful implied usage. It never states when an agent should call this versus paribu_get_ticker or paribu_get_orderbook, so the when-to-use 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.