Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_new_delivery_price

Retrieve the new delivery price for options. Specify category and base coin, with BTC as default.

Instructions

Get new delivery price for options.

Args: category: Product type: option. base_coin: Base coin (default: BTC).

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

Input Schema

NameRequiredDescriptionDefault
categoryNooption
base_coinNoBTC

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?

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the tool gets a price, but does not disclose whether it is read-only, what data it returns, or any dependencies. This is insufficient for safe agent invocation.

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 very short (two sentences) with no superfluous content. It is front-loaded with the core purpose. However, the brevity sacrifices necessary detail for 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 output schema and minimal parameter coverage (0% schema description), the description should provide more context about the return value, typical use cases, or prerequisite conditions. It does not, leaving the agent underinformed.

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?

Schema description coverage is 0%, so the description must add meaning beyond the schema. It merely restates the parameter names and defaults already present in the input schema ('category: Product type: option' and 'base_coin: Base coin (default: BTC)'), adding no deeper semantics 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 states 'Get new delivery price for options,' which clearly indicates the verb (get), resource (new delivery price), and context (options). However, it does not differentiate from the sibling tool 'get_delivery_price,' leaving ambiguity about what 'new' specifically entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'for options,' providing context that this tool is specific to options. However, no explicit guidance is given on when to use this versus alternatives like 'get_delivery_price,' nor are there any exclusions or recommended scenarios.

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