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

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

paribu_get_recent_trades

Retrieve recent public trades for a Paribu market in reverse chronological order, with an optional limit from 1 to 20.

Instructions

Most recent public trades for one market, newest first. market: e.g. "btc_tl". limit 1..20 (the API maximum).

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": {
      "market": "<market>"
    },
    "name": "paribu_get_recent_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
marketYes

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 burden, and it does disclose useful traits: trades are public, results are ordered newest first, and the limit is capped at the API maximum of 20. It does not state whether the call is read-only (implied), any rate limits, or what happens when limit exceeds 20, leaving real gaps for an unannotated 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?

Two short sentences, front-loaded with the core purpose and ordering, followed by the parameter constraints. No filler or redundant restatement of the tool name.

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 explained, and both parameters are addressed in the description. The main missing piece is routing guidance relative to sibling market-data tools, which keeps it from a 5.

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 does: it gives a concrete market format example ('btc_tl') and the valid limit range 1..20 with the note that 20 is the API maximum. It omits the default limit of 10 declared in the schema, which is the only notable gap.

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 ('most recent public trades for one market') plus an ordering guarantee ('newest first'), which is enough to distinguish it from siblings like get_orderbook or get_ticker. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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 when-to-use or when-not-to-use guidance and no mention of alternatives such as get_orderbook or get_ticker for depth/history. The agent must infer that this is the tool for recent trade prints from the purpose sentence alone.

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