Skip to main content
Glama

midasflow-mcp-quickstart

by io.github.midasflowai-lab

Get order-book snapshot (walls / imbalance + S/R)

get_orderbook
Read-onlyIdempotent

Live order-book snapshot for a symbol — bid/ask walls, book imbalance, spread — FOLDED with support/resistance levels (classic TA fused with cross-exchange book walls + Fibonacci) so you see resting liquidity AND the level map in one call. Cross-exchange aggregate, derived levels only. Market DATA, not advice; thin/uncovered symbols return null fields (normal). Routes: /v1/orderbook/{symbol} + folds /v1/sr as sr.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesPerp symbol, e.g. 'BTCUSDT' (case/space-insensitive). Resolves the cross-venue aggregate.
include_srNoIf true (default), fold support/resistance + Fibonacci levels (/v1/sr) into the response under `sr`. Set false to skip.
sr_timeframeNoTimeframe for the folded S/R computation. Default '1h'.1h

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds details: cross-exchange aggregate, derived levels only, and that thin/uncovered symbols return null fields. No contradiction with annotations.

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 four sentences, front-loaded with the main functionality. It is concise but contains necessary technical details; minor redundancy could be trimmed but overall efficient.

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?

Given the presence of an output schema, the description does not need to detail return values. It covers the tool's core function, edge cases (null fields), and the folding of S/R levels. It is complete enough for effective use.

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

Parameters4/5

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

Schema coverage is 100% with good parameter descriptions. The description adds value by explaining the symbol parameter is case/space-insensitive and that include_sr defaults to true but can be set to false. It also mentions the default timeframe for sr_timeframe.

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 it provides a live order-book snapshot with bid/ask walls, book imbalance, spread, and folded support/resistance levels. It specifies the resource (symbol) and verb (get), and distinguishes from siblings by the unique combination of order-book data and S/R levels.

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?

The description gives clear context: it's for order-book data with aggregated levels, notes thin symbols return null fields, and says 'market DATA, not advice'. It does not explicitly state when to avoid this tool or mention alternatives, but the context is sufficient for most use cases.

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

All midasflow-mcp-quickstart toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct aspect of market data and analytics: account info, analysis, backtesting, expected value, accuracy, candles, context, flow, heatmap, market overview, orderbook, signals, whales, and scoring. Despite some thematic overlap (e.g., get_accuracy and score_symbol both involve probabilities), descriptions clearly differentiate their purposes and usage contexts.

Naming Consistency2/5

Naming is inconsistent: some tools use the 'get_' prefix (get_accuracy, get_candles, etc.), while others are bare verbs or nouns (account, analyze, backtest, calc_ev, score_symbol). This mix of patterns (get_ vs verb vs noun) makes the naming convention unpredictable.

Tool Count5/5

With 14 tools, the server is well-scoped for a comprehensive market data and analytics API. Each tool serves a clear and distinct function, and the count is neither too few to cover the domain nor too many to be overwhelming.

Completeness5/5

The tool set covers all major aspects of the domain: account management, historical data (candles), market context (regime, flow, heatmap), order book, signals, accuracy/backtesting, and scoring. There are no obvious missing operations for an analytics-focused financial data server.

Resources