Skip to main content
Glama

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

TableJSON 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 structure has this many rounds, a round being one rung of the ladder. Only 4 and 5 exist. 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: above 4.5 reads Strong, above 3.75 Favorable, above 3.25 Moderate, below that Misaligned. Default: 0 (no filter).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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."
  3. 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."
  4. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "crypto",
-  "stock",
-  "commodity"
-]New value: +[
+  "crypto",
+  "stock"
+]
  5. 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=true, so the safety profile is covered. The description adds genuinely useful behavior: the tool returns a ranked list, answers in formatted text, and costs 3 quota units. It does not overclaim any side effects.

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 first sentence front-loads purpose and the routing guidance follows immediately; the quota cost is a useful closing note. It is slightly redundant ('find instruments...' then 'filter by...') and 'and more' is vague, but overall tight.

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?

With six parameters fully documented in the schema, no output schema, and read-only annotations, the description covers the important invocation context: ranked result, formatted text, quota cost, and when not to use it. It stops just short of describing the result items, which would make it fully complete.

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?

Schema description coverage is 100% and every parameter has a rich description in the schema, so the tool description is not required to carry parameter detail. It restates the main filter dimensions but adds no syntax or semantics beyond the schema.

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 ('find') and resource ('instruments matching criteria across an asset class'), and immediately distinguishes itself from list_top_crypto/list_top_stocks by naming the filters that require it. An agent can tell what it does and why it differs from siblings.

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?

Explicitly gives the selection rule: use when a filter other than count/Startingale floor is needed, and names the exact alternatives for the simpler cases and the no-condition case. This is model routing guidance.

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