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

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

paribu_get_orderbook

Fetch a live Paribu order book for a specified market to see best bid/ask, spread, mid price, and up to 100 price levels per side.

Instructions

Live order book for one market: best bid/ask, spread, mid price and the price levels on each side. market: e.g. "btc_tl". limit 1..100 price levels per side (default 20).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
marketYes

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?

With no annotations, the description must carry the behavioral burden. It discloses that the data is 'live' and what fields/sides are returned, but says nothing about whether this is a point-in-time snapshot versus a stream, whether the call is public or needs auth, or any rate-limit behavior. An output schema exists, so return-shape detail is fairly excused, but operational traits remain undisclosed.

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 tight sentences with zero filler; the core purpose and returned fields come first, followed by the parameter clarifications. Every clause earns its place, despite a slightly awkward line break mid-sentence.

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?

For a 2-parameter read tool with an output schema, the description covers purpose, returned content, and both parameters with constraints. The remaining gap is operational context (snapshot semantics, auth/public status), which is minor but not negligible given the absence of annotations.

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%, so the description does the heavy lifting: it gives a concrete market format example ('btc_tl'), states the limit range 1..100, clarifies that limit counts price levels per side, and gives the default of 20. That is substantial added meaning, with only minor gaps such as case sensitivity or supported market naming variants.

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 ('Live order book for one market') and enumerates the returned content: best bid/ask, spread, mid price, and per-side price levels. An agent can tell this apart from ticker/trades siblings by the resource name alone, 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?

Usage is implied by the resource description (fetch a live book for a single market) but there is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as paribu_get_ticker or paribu_get_recent_trades. Adequate but leaves the agent to infer the choice.

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