Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_fiat_convert_history

Retrieve past fiat currency conversions. Optionally limit the number of records returned for efficiency.

Instructions

Get fiat conversion history.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

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?

No annotations are provided, so the description carries full burden. The tool is implied to be read-only ('get'), but no behavioral traits like authentication needs, rate limits, or data freshness are disclosed. The description only states the purpose and the limit parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of two sentences with no unnecessary words. It front-loads the purpose and describes the parameter efficiently.

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 low schema coverage (0%) and no output schema, the description should provide more context about what the history contains (e.g., fields returned, date range, pagination). It only mentions the limit parameter, leaving significant information gaps for the agent.

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

Parameters3/5

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

The single parameter 'limit' is described as 'Number of records (default: 50)', which adds meaning beyond the schema (which only has a default value and type). This is adequate for a simple parameter, but no further parameter details are provided (e.g., valid range).

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?

Description states 'Get fiat conversion history' which clearly identifies the tool as retrieving historical conversion data for fiat currencies. It distinguishes from siblings like get_convert_history (likely crypto) and get_fiat_balance, but does not explicitly differentiate from similar history tools.

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 (e.g., get_convert_history, get_fiat_convert_status). There is no mention of prerequisites, limitations, or typical use cases.

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