Skip to main content
Glama
Sign In

Tradingale-mcp

by com.tradingale
OverviewDiscussionsAdmin

search_instruments

Read-only

THE QUERY TOOL: find instruments matching criteria across an asset class. Filter by minimum Martingale score, minimum Startingale, exchange and more; returns a ranked list. Use it when a filter OTHER than count or Startingale floor is needed: exchange, round count, or a minimum Martingale Score. If the only conditions are how many and a Startingale floor, list_top_crypto or list_top_stocks do the same in one step; for no conditions at all, use an overview. Answers in formatted text. Costs 3 units of the monthly quota.

Input Schema

NameRequiredDescriptionDefault
typeNoWhich catalogue to search. One at a time, not both. Default: crypto.
limitNoHow many to return, highest Martingale Score first. 1-20, default 10.
roundsNoKeep only instruments whose sequence has this many rounds: the total number of orders, initial round included (4 or 5). Omit for both.
exchangeNoKeep only instruments that venue lists. Exactly one of: binance, kraken_pro (note the underscore), hyperliquid. This is a listing fact about the market, reported for callers who run their own execution; Tradingale places no orders on any venue, so it says nothing about where you can or should trade. Crypto only, stocks ignore it. Omit to search every venue.
min_martingaleNoKeep only instruments at or above this Martingale Score. Scale 0-5, higher means the price behaviour fits the sequence structure better. Above 4 is the usual starting point for a shortlist. Default: 0 (no filter).
min_startingaleNoKeep only instruments at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which is about behaviour over time. Scale 0-5: 4.3 and above reads Strong, 3.7 and above Favorable, 3 and above Moderate, below that Misaligned. Default: 0 (no filter).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rounds / description
      Previous value: -"Keep only instruments whose sequence structure has this many rounds, a round being one rung of the ladder. Only 4 and 5 exist. Omit for both."New value: +"Keep only instruments whose sequence has this many rounds: the total number of orders, initial round included (4 or 5). Omit for both."
  2. Changed1 schema field changed
    • changedInput schema / properties / min_startingale / description
      Previous value: -"Keep only instruments at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which is about behaviour over time. Scale 0-5: above 4.5 reads Strong, above 3.75 Favorable, above 3.25 Moderate, below that Misaligned. Default: 0 (no filter)."New value: +"Keep only instruments at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which is about behaviour over time. Scale 0-5: 4.3 and above reads Strong, 3.7 and above Favorable, 3 and above Moderate, below that Misaligned. Default: 0 (no filter)."
  3. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many to return, best Martingale Score first. 1-20, default 10."New value: +"How many to return, highest Martingale Score first. 1-20, default 10."
    • changedInput schema / properties / min_startingale / description
      Previous value: -"Keep only instruments at or above this Startingale reading — how well the CURRENT price sits versus the structure, unlike the Martingale Score which is about behaviour over time. Scale 0-5: above 4.5 reads Strong, above 3.75 Favorable, above 3.25 Moderate, below that Misaligned. Default: 0 (no filter)."New value: +"Keep only instruments at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which is about behaviour over time. Scale 0-5: above 4.5 reads Strong, above 3.75 Favorable, above 3.25 Moderate, below that Misaligned. Default: 0 (no filter)."
    • changedInput schema / properties / rounds / description
      Previous value: -"Keep only instruments whose sequence structure has this many rounds — a round being one rung of the ladder. Only 4 and 5 exist. Omit for both."New value: +"Keep only instruments whose sequence structure has this many rounds, a round being one rung of the ladder. Only 4 and 5 exist. Omit for both."
  4. Changed1 schema field changed
    • changedInput schema / properties / exchange / description
      Previous value: -"Keep only instruments listed on that venue. Exactly one of: binance, kraken_pro (note the underscore), hyperliquid. Crypto only — stocks ignore it. Omit to search every venue."New value: +"Keep only instruments that venue lists. Exactly one of: binance, kraken_pro (note the underscore), hyperliquid. This is a listing fact about the market, reported for callers who run their own execution; Tradingale places no orders on any venue, so it says nothing about where you can or should trade. Crypto only, stocks ignore it. Omit to search every venue."
  5. Changed6 schema fields changed
    • changedInput schema / properties / exchange / description
      Previous value: -"Filter by exchange availability"New value: +"Keep only instruments listed on that venue. Exactly one of: binance, kraken_pro (note the underscore), hyperliquid. Crypto only — stocks ignore it. Omit to search every venue."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results to return. Default: 10, Max: 20"New value: +"How many to return, best Martingale Score first. 1-20, default 10."
    • changedInput schema / properties / min_martingale / description
      Previous value: -"Minimum Martingale score (0-5). Default: 0"New value: +"Keep only instruments at or above this Martingale Score. Scale 0-5, higher means the price behaviour fits the sequence structure better. Above 4 is the usual starting point for a shortlist. Default: 0 (no filter)."
    • changedInput schema / properties / min_startingale / description
      Previous value: -"Minimum Startingale value (0-5). Default: 0"New value: +"Keep only instruments at or above this Startingale reading — how well the CURRENT price sits versus the structure, unlike the Martingale Score which is about behaviour over time. Scale 0-5: above 4.5 reads Strong, above 3.75 Favorable, above 3.25 Moderate, below that Misaligned. Default: 0 (no filter)."
    • changedInput schema / properties / rounds / description
      Previous value: -"Filter by number of rounds"New value: +"Keep only instruments whose sequence structure has this many rounds — a round being one rung of the ladder. Only 4 and 5 exist. Omit for both."
    • changedInput schema / properties / type / description
      Previous value: -"Asset type to search. Default: crypto"New value: +"Which catalogue to search. One at a time, not both. Default: crypto."
  6. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "crypto",
-  "stock",
-  "commodity"
-]New value: +[
+  "crypto",
+  "stock"
+]
  7. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the quota cost ('Costs 3 units of the monthly quota') and the output form ('Answers in formatted text'), which the agent could not infer otherwise. It also states results are ranked, though it doesn't expand on ordering beyond what the schema's limit description covers.

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?

Front-loaded with a scope statement, then alternatives, then cost — the important routing information comes first. It is dense but slightly repetitive in restating 'Startingale floor' twice in adjacent sentences.

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 6-param read-only search with no output schema, the description covers scope, alternatives, ranking, output format, and quota cost. What remains uncovered (pagination, what a 'formatted text' response actually looks like) is minor for a read tool with a hard limit of 20.

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%, so the baseline is 3, but the description adds the practical distinction that exchange/rounds/min_martingale are the discriminating filters and that a Startingale floor alone doesn't justify this tool. That framing helps parameter selection beyond the per-field schema text.

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?

States a specific verb and resource ('find instruments matching criteria across an asset class'), plus the return shape ('returns a ranked list'). It is immediately distinguishable from list_top_crypto, list_top_stocks, and the overview siblings by naming them as narrower alternatives.

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

Usage Guidelines5/5

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

Gives an explicit decision rule: use this when a filter other than count or a Startingale floor is needed (exchange, round count, minimum Martingale Score). It then routes the two excluded cases to named siblings — list_top_crypto/list_top_stocks for count+floor, and an overview for no conditions.

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

All Tradingale-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources