Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

new_crypto_loan_fixed_renew

Renew a fixed crypto loan borrow order by providing the loan ID to extend the borrow period.

Instructions

Renew a fixed crypto loan borrow order.

Args: loan_id: Loan ID.

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": {
      "loan_id": "<loan_id>"
    },
    "name": "new_crypto_loan_fixed_renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
loan_idYes

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?

The description only states the action ('Renew') without disclosing behavioral traits such as required permissions, reversibility, side effects on the original loan, or rate limits. Since no annotations exist, the description carries the full burden, and it falls short.

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 extremely concise (two sentences) and front-loaded with the core purpose. However, it sacrifices completeness; a slightly longer description could add value without losing conciseness.

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, no annotations, and a single parameter, the description is incomplete. It fails to explain what 'renew' entails (e.g., extend duration, adjust terms) or what the result is, leaving the agent without sufficient context to invoke the tool confidently.

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 sole parameter 'loan_id' is described merely as 'Loan ID,' which adds no meaning beyond the input schema's title. With 0% schema description coverage, the description should compensate by explaining format, source, or constraints, but it does not.

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 explicitly states 'Renew a fixed crypto loan borrow order,' which uses a specific verb (renew) and clearly identifies the resource. This action is distinct from sibling tools like new_crypto_loan_fixed_borrow (create) or new_crypto_loan_fixed_repay (repay), making its purpose unambiguous.

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. It does not mention prerequisites, context (e.g., existing loan must be in a renewable state), or when to avoid using it. Sibling tools are listed but without differentiation criteria.

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