Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_new_crypto_loan_loanable_data

Retrieve available coins for crypto loans with an optional currency filter to find specific loanable assets.

Instructions

Get new crypto loan loanable coin data.

Args: currency: Filter by currency (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_new_crypto_loan_loanable_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.3/5.0
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as read-only nature, authentication requirements, data freshness, or pagination. It only states the basic function, leaving the agent unaware of side effects or limitations.

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 very short and front-loaded, but it lacks structure (e.g., sections). While concise, it is under-specified for the tool's context and does not fully earn its brevity by omitting important information.

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

Completeness1/5

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

Given the tool's context (many sibling tools, no output schema, one parameter), the description is severely incomplete. It fails to define 'new crypto loan loanable data,' explain return values, or differentiate from similar tools, making it inadequate for correct selection and invocation.

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 schema parameter 'currency' has 0% description coverage. The description merely restates 'Filter by currency (optional),' which adds no meaning beyond the schema. It does not explain valid values, format, or behavior when omitted.

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 'Get new crypto loan loanable coin data,' specifying a verb and resource. However, it does not distinguish from sibling tools like get_crypto_loan_loanable_data or other get_new_crypto_loan_* tools, leaving ambiguity about the exact scope.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools exist for similar data, but the description offers no criteria for selection, such as stating that this tool provides loanable coin data for the 'new' loan system.

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