Skip to main content
Glama

midasflow-mcp-quickstart

by io.github.midasflowai-lab

Get Flow signals (live feed / elite crown)

get_signals
Read-onlyIdempotent

Pull recent MidasFlow SignalEvent records (newest first). quality='normal' (default) = the bucketed signal log across source families; quality='elite' = the rare highest-conviction multi-model-consensus crown feed (premium+, lagged anti-front-run). Tier-gated + moat-scrubbed server-side. Market DATA, not advice. Routes: normal→/v1/signals/pull, elite→/v1/signals/elite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax events to return (normal 1-200, elite 1-50; clamped server-side). Default 20.
cursorNoPagination cursor (normal feed only) — pass 'next_cursor' from the previous page for older events (0 = newest).
sourceNoSource-family filter: '' / 'all' | 'pump' | 'flow' | 'mfb' (case/space-insensitive). Ignored when quality='elite'.
symbolNoSingle symbol filter, e.g. 'BTCUSDT' (empty = all symbols).
qualityNo'normal' (default, /v1/signals/pull) | 'elite' (crown consensus feed, /v1/signals/elite, premium+).normal

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.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint true and destructiveHint false, indicating a safe read operation. The description adds valuable context: 'Tier-gated + moat-scrubbed server-side' and 'Market DATA, not advice,' which helps the agent understand access restrictions and legal disclaimers. No contradictions.

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 a single paragraph that efficiently covers purpose, quality variants, gating, and routing. It is concise but packs significant information; could benefit from slight restructuring but remains clear.

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

Completeness5/5

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

Given the complexity (5 optional params, output schema present), the description is comprehensive. It explains the two feed qualities, filtering options, pagination via cursor, server-side clamping, and legal disclaimer. The presence of an output schema means return values are covered elsewhere, so no gaps.

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 description coverage is 100%, so parameters are already well documented. The description adds extra context beyond the schema, such as the routing differences ('normal→/v1/signals/pull, elite→/v1/signals/elite') and the nature of elite as 'lagged anti-front-run,' which aids in parameter selection.

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 pulls recent MidasFlow SignalEvent records, distinguishes between 'normal' and 'elite' qualities, and even gives the specific API routes. This sets it apart from sibling tools like get_flow or get_candles.

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 explains when to use normal vs elite quality, noting that elite is premium+ and has lag. However, it does not explicitly compare with sibling tools or state when not to use this tool, though the context makes it fairly clear.

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