Skip to main content
Glama
miratcan

Simsar MCP

by miratcan

get_top_trader_ratio

Check the top trader long/short ratio to follow whale activity and gain a more reliable market signal than overall positions.

Instructions

Get top trader long/short ratio.

Shows what the top traders (whales) are doing. More reliable signal than overall ratio - follow the smart money.

Args: symbol: Trading pair symbol (e.g., BTCUSDT, ETHUSDT)

Returns: Top trader long/short ratio and percentages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits such as data frequency, definition of 'top traders', or error handling. Minimal transparency.

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?

Description is concise and well-structured: a clear one-line summary, explanatory sentence, then Args/Returns. No filler.

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

Completeness3/5

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

Adequate for a simple one-parameter tool with an output schema. Lacks details like update frequency and definition of top traders, but overall sufficient.

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?

With 0% schema coverage, description adds a format example (e.g., BTCUSDT) and notes it's a trading pair. This adds value beyond the schema's 'string' type but lacks depth.

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?

Clearly states it gets the top trader long/short ratio and distinguishes from overall ratio by noting it's a more reliable signal from whales. Sibling tool get_long_short_ratio exists, and this description explicitly contrasts.

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

Usage Guidelines4/5

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

Implies use when following smart money and contrasts with overall ratio. However, no explicit when-not or prerequisites are given.

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/miratcan/simsar-mcp'

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