Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

confirm_convert_quote

Confirm a crypto conversion quote using its transaction ID to finalize the exchange.

Instructions

Confirm a crypto-to-crypto conversion quote.

Args: quote_tx_id: Quote transaction ID.

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": {
      "quote_tx_id": "<quote_tx_id>"
    },
    "name": "confirm_convert_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_tx_idYes

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 are provided, and the description fails to disclose effects like whether confirming executes the conversion, idempotency, or authentication requirements. 'Confirm' implies a write operation but lacks detail.

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?

The description is very short (two sentences) and front-loaded with the purpose, appropriate for a tool with one parameter. However, it omits important contextual information, earning a slightly lower score for being too sparse.

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?

Given the tool is part of a conversion workflow with sibling tools like 'request_convert_quote', the description should explain that the quote must be obtained first or what happens after confirmation. It has no output schema, so return values or effects need description.

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?

The description adds minimal value beyond the schema: it repeats 'Quote transaction ID' which is essentially the schema title. With 0% schema description coverage, it should provide more context, such as how to obtain the ID or format expectations.

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 the tool confirms a crypto-to-crypto conversion quote, using specific verb 'confirm' and resource 'convert quote'. It distinguishes from siblings like 'confirm_fiat_quote' and 'confirm_small_balance_quote'.

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 prerequisites or when to use this tool vs alternatives. It does not mention that it should follow 'request_convert_quote' or that it executes the conversion.

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