Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_fiat_convert_status

Retrieve the current status of a fiat currency conversion. Specify a trade number or merchant request ID to get details.

Instructions

Get fiat conversion status.

Args: trade_no: Trade number (optional). merchant_request_id: Merchant request ID (optional).

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": "get_fiat_convert_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
trade_noNo
merchant_request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'Get fiat conversion status' and lists parameters, but does not disclose that it is a read-only operation, any side effects, or required permissions.

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?

Very short and to the point, but includes unnecessary Python docstring formatting ('Args:'). Still, every sentence serves a purpose and it is not verbose.

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?

For a status-check tool with no output schema and no annotations, the description should explain what the status represents and what the response contains. It does not provide that context, leaving the agent with insufficient information.

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

Parameters2/5

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

Schema description coverage is 0%, but the description only repeats parameter names and indicates optionality (already implied by schema). It adds no semantic meaning beyond the schema, such as format constraints or usage examples.

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 clearly states 'Get fiat conversion status' with a specific verb and resource. Among siblings, it distinguishes from 'get_convert_status' and 'get_fiat_convert_history' by focusing on fiat conversion status.

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 on when to use this tool versus alternatives like 'get_convert_status' or 'get_fiat_convert_history'. The parameters are listed but no criteria for choosing between trade_no and merchant_request_id.

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