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

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

paribu_get_currency

Retrieves Paribu currency metadata such as type, precision, listing date, deposit/withdrawal limits, and per-network withdrawal fees, helping users verify a coin's trading and transfer details.

Instructions

Currency metadata from the exchange config: name, type, precision/step, listing date, deposit and withdrawal limits, and per-network details (name, estimated arrival, explorer link, withdrawal fee). currency: e.g. "btc", "eth", "usdt", "xrp".

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": {
      "currency": "<currency>"
    },
    "name": "paribu_get_currency"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 behavioral burden. It does disclose a meaningful trait by stating the data comes 'from the exchange config', implying a static reference read with no side effects, and it lists the domains of returned data. It does not say what happens for an unknown or unsupported symbol (error vs. empty), whether symbols are case-sensitive, or whether the config is cached.

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?

Two compact sentences, front-loaded with the resource and its returned fields, followed by the parameter example. The field enumeration is dense but each item is informative rather than restated boilerplate; nothing is redundant, though it reads as a list rather than a routing statement.

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 one-parameter read tool with an output schema present, the description covers purpose, returned field domains, and parameter format, which is close to sufficient. The remaining gap is failure behavior for an invalid symbol, which an agent would want before calling.

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% and the single parameter has only a title, so the description must compensate, and it does: it names the parameter and gives concrete example values ("btc", "eth", "usdt", "xrp"), communicating the expected lowercase ticker format. It stops short of clarifying case sensitivity or whether quote-currency pairs are accepted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get) and resource (currency metadata) and enumerates exactly what is returned: name, type, precision/step, listing date, deposit/withdrawal limits, per-network details. This clearly distinguishes it from the sibling market-data tools (orderbook, trades, ticker, market_movers), which return live pricing rather than static config metadata.

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 only implied by the nature of the tool: an agent can infer it should call this to learn a currency's precision, limits, or network withdrawal details. There is no explicit when-to-use statement, no statement of when not to use it, and no named alternative for related lookups such as listing a market.

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