Skip to main content
Glama
eliasfire617

Crypto Market Data MCP Server

get_long_short_ratio

Provides the long/short account ratio for Binance USDⓈ-M futures, enabling sentiment analysis of trader positioning over customizable time periods.

Instructions

Global long/short account ratio (Binance USDⓈ-M futures only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoBinance raw symbol, e.g. 'BTCUSDT' (no slash).BTCUSDT
periodNo'5m','15m','30m','1h','2h','4h','6h','12h','1d'.5m
limitNoNumber of data points (default 10, max 500).
exchangeNoMust be 'binance' (only supported venue for this metric here).binance

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries the full burden. It discloses the metric is a ratio and the venue, but omits details on data aggregation, update frequency, or any rate limits.

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?

A single sentence with no wasted words, though it could include a bit more context without harming conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values are covered. The description is adequate for a simple metric tool but lacks caveats like data availability only for certain symbols.

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?

Schema coverage is 100%, so the schema documents parameters. The description adds no extra meaning beyond 'global' and 'futures only', which is already implied by the tool name.

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 tool returns a global long/short account ratio specifically for Binance USDⓈ-M futures, which distinguishes it from sibling tools like get_funding_rate or get_open_interest.

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?

The description mentions it's only for Binance futures but provides no guidance on when to use this tool versus alternatives like get_funding_rate or get_liquidations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eliasfire617/crypto-market-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server