Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

request_fiat_quote

Request a quote for converting between fiat and cryptocurrencies. Specify source and destination assets, types, and amount to get the conversion rate.

Instructions

Request a fiat conversion quote.

Args: from_coin: Source coin/currency. from_coin_type: Source type: crypto, fiat. to_coin: Destination coin/currency. to_coin_type: Destination type: crypto, fiat. request_amount: Amount.

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": {
      "from_coin": "<from_coin>",
      "from_coin_type": "<from_coin_type>",
      "to_coin": "<to_coin>",
      "to_coin_type": "<to_coin_type>",
      "request_amount": "<request_amount>"
    },
    "name": "request_fiat_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
from_coinYes
from_coin_typeYes
to_coinYes
to_coin_typeYes
request_amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, and the description fails to disclose behavioral traits beyond the basic action. It does not mention side effects, authentication needs, rate limits, or what happens after requesting a quote.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the action, but it includes a parameter list that adds redundancy with the schema. It could be more concise, but the parameter descriptions are necessary given the schema's lack of descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Without annotations, output schema, or sibling differentiation, the description is insufficient. It does not explain what a 'fiat quote' entails, how amounts are interpreted, or any constraints. The tool is one of many similar quote tools, but no differentiation is provided.

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

Parameters3/5

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

The description includes brief parameter explanations (e.g., 'from_coin: Source coin/currency'), which add some value over the bare schema names. However, the explanations are minimal and lack format details or constraints, so they only partially compensate for the 0% schema coverage.

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?

The description 'Request a fiat conversion quote' clearly states the verb and resource, distinguishing it from siblings like 'request_convert_quote' (crypto) and 'confirm_fiat_quote' (confirmation). It is specific and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like 'request_convert_quote' or 'confirm_fiat_quote'. There is no mention of prerequisites, context, or when not to use it.

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

Deploy Server

Other Tools