Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

new_crypto_loan_adjust_ltv

Modify collateral for a new crypto loan by specifying currency, amount, and direction (add or reduce).

Instructions

Adjust collateral amount for new crypto loan.

Args: currency: Collateral currency. amount: Adjustment amount. direction: Direction: add, reduce.

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>",
      "amount": "<amount>",
      "direction": "<direction>"
    },
    "name": "new_crypto_loan_adjust_ltv"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYes
amountYes
directionYes

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 must disclose behavioral traits. It only says 'adjust' without stating effects on LTV, risks, authorization needs, or rate limits. Minimal transparency.

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 short and to the point with one line and bullet list. No wasted words, though it could be more structured.

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 no output schema and no annotations, the description is incomplete. It does not explain return values, confirmation, or whether the operation is synchronous. A simple mutation tool needs more context.

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?

Schema coverage is 0%, so description must add meaning. It defines currency as 'Collateral currency', amount as 'Adjustment amount', and direction as 'add, reduce'. This adds basic interpretation but lacks constraints (e.g., enum for direction, amount format).

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?

The description clearly states the action 'Adjust collateral amount for new crypto loan', which is specific. However, it does not explicitly differentiate from the sibling 'crypto_loan_adjust_ltv', though the tool name includes 'new'.

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 'crypto_loan_adjust_ltv' or other loan adjustment tools. No prerequisites or conditions provided.

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