Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_new_crypto_loan_fixed_supply_contract

Retrieve fixed crypto loan supply contract details, with optional filtering by currency and record limit.

Instructions

Get fixed crypto loan supply contract info.

Args: supply_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_supply_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
supply_currencyNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, and the description only states it retrieves info, implying a read operation. It does not disclose any behavioral traits such as whether it requires authentication, data freshness, or potential side effects.

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 detail needed for clarity. It is not verbose, but its conciseness comes at the cost of completeness.

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 lack of annotations, no output schema, and only two parameters with minimal descriptions, the description is incomplete. It does not explain what the output contains, any constraints, or how it relates to similar sibling tools.

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 semantics: 'Filter by currency' for supply_currency and 'Number of records' for limit. With 0% schema description coverage, the description should compensate but only provides basic, generic descriptions similar to the schema names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it retrieves fixed crypto loan supply contract info, but it doesn't specify what info is returned or how it differs from sibling tools like get_new_crypto_loan_fixed_supply_market or get_new_crypto_loan_fixed_contract_info. The verb 'Get' and resource are present, but lack specificity.

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 given on when to use this tool versus alternatives. The description merely mentions optional parameters without indicating use cases, prerequisites, or exclusions.

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