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

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

paribu_market_movers

Retrieve top 24-hour gainers or losers on Paribu ranked by percentage change, with optional TL or USDT quote filtering and a configurable result limit.

Instructions

Top gainers or losers on Paribu over the last 24h, ranked by percentage change. direction: "gainers" (default) or "losers". quote: filter to "tl" or "usdt" (omit for all). limit 1..50.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
quoteNo
directionNogainers

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden; it does convey the 24h window, the ranking metric, and that omitting quote returns all quotes, which establishes this as a read-only snapshot call. It omits rate-limit behavior, what happens with an invalid direction string, and whether results are paginated, leaving real gaps for a no-annotation tool.

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?

Three compact fragments, front-loaded with what the tool returns before covering each parameter. There is no filler, no restatement of the name, and every line adds usable information.

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?

With an output schema present, the description need not explain return values, and all three parameters are addressed despite zero schema coverage. Completeness is slightly short of ideal only because error and edge-case behavior for a no-annotation tool is left unstated.

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 description coverage is 0%, so the description must compensate, and it largely does: it enumerates direction values with the default, names the acceptable quote values (tl, usdt) and the omit-for-all semantics, and gives the limit range 1..50. The only gap is the limit default of 10, which lives in the schema but not the 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?

The description opens with a specific verb-and-resource statement: 'Top gainers or losers on Paribu over the last 24h, ranked by percentage change,' which tells an agent exactly what data comes back and the ranking basis. It does not name or distinguish itself from any sibling (list_markets, get_ticker), but the resource is distinct enough to stand on its own.

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?

Usage is implied through default values ('gainers' default, omit quote for all) rather than stated as conditions for choosing this tool over paribu_get_ticker or paribu_list_markets. There is no explicit when-to-use or when-not-to-use guidance, and no mention of prerequisites such as needing a market universe to exist first.

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