Skip to main content
Glama
Sign In
edgex-mcp

edgex-mcp

by realnaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edgex_get_ratio

Aggregate long/short position ratios from multiple exchanges (Binance, OKX, Bybit) for any symbol, giving a quick view of market sentiment.

Instructions

Get long/short ratio aggregated from multiple exchanges (Binance, OKX, Bybit, etc.).

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": "edgex_get_ratio"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoe.g. BTC, ETH, SOL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description takes on the burden; it adds the aggregation behavior across exchanges but doesn't disclose auth requirements, pagination, or response format.

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?

One concise sentence, front-loaded with the action and resource, with no wasted words.

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?

For a simple getter with one parameter and no output schema, the description covers the core purpose and data scope, but lacks explicit return value details; acceptable given the low complexity.

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 schema fully describes the single 'symbol' parameter with examples, and the description doesn't add further semantic detail, so baseline 3.

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 uses the specific verb 'Get' with the resource 'long/short ratio' and specifies aggregation across exchanges, clearly distinguishing it from sibling data tools like get_ticker or get_depth.

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 on when to choose this tool over siblings; the description doesn't mention alternatives or conditions, leaving the agent to infer from the name.

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