Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_new_crypto_loan_fixed_borrow_order

Retrieve fixed crypto loan borrow order details. Filter by order currency and limit the number of records.

Instructions

Get fixed crypto loan borrow order info.

Args: order_currency: Filter by currency (optional). limit: Number of records (default: 50).

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_new_crypto_loan_fixed_borrow_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_currencyNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only implies a read operation via the verb 'Get' but fails to disclose any additional behaviors such as authentication requirements, rate limits, pagination details, or error conditions.

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

Conciseness5/5

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

The description is extremely concise—two sentences plus an Args block—with no extraneous content. The main purpose is stated first, and parameter details follow in a structured list.

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

Completeness3/5

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

Given the large set of sibling tools and no output schema, the description is somewhat under-specified. It explains the parameters but does not describe the return value, how this tool relates to other loan tools, or provide any examples. This is adequate for a simple get operation but leaves room for confusion.

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 adds basic explanations for both parameters: 'Filter by currency' for order_currency and 'Number of records' for limit. While the schema already provides defaults and types, the description clarifies their purpose. However, the explanations are minimal and do not cover possible values or constraints.

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 verb ('Get') and the resource ('fixed crypto loan borrow order info'), distinguishing it from many sibling tools like get_new_crypto_loan_fixed_supply_order or get_new_crypto_loan_fixed_borrow_market. However, it does not specify what 'info' includes or how the result differs from similar tools.

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 its many siblings (e.g., get_new_crypto_loan_fixed_borrow_market, get_new_crypto_loan_ongoing_orders). There are no conditions, prerequisites, or alternatives mentioned, leaving the agent to guess.

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