Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_new_crypto_loan_max_collateral

Get the maximum allowable collateral reduction for a new crypto loan by specifying the collateral currency.

Instructions

Get max allowed collateral reduction amount (new crypto loan).

Args: currency: Collateral currency.

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>"
    },
    "name": "get_new_crypto_loan_max_collateral"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It only states 'Get max allowed collateral reduction amount', lacking any mention of read-only nature, auth requirements, rate limits, or error handling. The description is insufficient for safe operation.

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 brief (two sentences plus arg list), but the brevity sacrifices necessary context. It is not overly verbose, but it lacks structure for easy scanning. An acceptable minimal length but not optimally informative.

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 single parameter, no output schema, and no annotations, the description should provide comprehensive context. It fails to explain what 'max allowed collateral reduction amount' means, how it is computed, or any related constraints (e.g., loan status, time limits). The description is incomplete for a clear understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must add meaning beyond the schema. It simply repeats 'currency: Collateral currency', adding no value about acceptable values, format, or constraints. This fails to compensate for the lack of schema documentation.

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 verb 'Get' and the resource 'max allowed collateral reduction amount (new crypto loan)', which is specific and distinguishes it from sibling tools like 'get_crypto_loan_max_collateral' and 'get_new_crypto_loan_max_loan'.

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 alternatives. There is no mention of context, prerequisites, or conditions for use, leaving the agent without decision support.

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