Skip to main content
Glama

Tradingale-mcp

by com.tradingale
OverviewDiscussionsAdmin

get_instrument

Read-only

ONE named instrument, in full. Returns the Martingale Score (0-5), the current Startingale reading, the score breakdown, the sequence structure (spacing, rounds, quantity multipliers) and exchange availability for a single crypto or US stock. Use this when you already know the symbol; use search_instruments to find symbols. Answers in formatted text, not JSON. Costs 1 unit of the monthly quota: the cheapest call, so walking a handful of known symbols one by one is fine.

Input Schema

NameRequiredDescriptionDefault
typeNoWhich catalogue to answer from: crypto or stock. Optional. Without it, both are searched; if the symbol exists in both (some tickers are a coin and a US stock), the answer lists both and asks you to call again with a type. With it, that catalogue answers, and the other is tried only if the symbol is not found.
symbolYesTicker symbol, not a name: BTC (not Bitcoin), ETH, SOL for crypto; AAPL, NVDA, MELI for US stocks. Case-insensitive. Use search_instruments if you only know the name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / description
      Previous value: -"Which catalogue to look in first. Default: crypto. Only an optimisation: if the symbol is not there, the other catalogue is searched automatically, so omitting this is safe."New value: +"Which catalogue to answer from: crypto or stock. Optional. Without it, both are searched; if the symbol exists in both (some tickers are a coin and a US stock), the answer lists both and asks you to call again with a type. With it, that catalogue answers, and the other is tried only if the symbol is not found."
  2. Changed2 schema fields changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker symbol (e.g., BTC, ETH, AAPL, GOLD)"New value: +"Ticker symbol, not a name: BTC (not Bitcoin), ETH, SOL for crypto; AAPL, NVDA, MELI for US stocks. Case-insensitive. Use search_instruments if you only know the name."
    • changedInput schema / properties / type / description
      Previous value: -"Asset type. Default: crypto. If not found, searches other types automatically."New value: +"Which catalogue to look in first. Default: crypto. Only an optimisation: if the symbol is not there, the other catalogue is searched automatically, so omitting this is safe."
  3. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "crypto",
-  "stock",
-  "commodity"
-]New value: +[
+  "crypto",
+  "stock"
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses that responses are formatted text rather than JSON, and that the call costs 1 unit of the monthly quota and is the cheapest call available. These are exactly the operational traits an agent needs before deciding to spend quota or parse output.

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?

Front-loaded with scope and return contents, then routing guidance, then cost. The return-value enumeration is long but justified because no output schema exists, so every clause earns its place.

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?

With no output schema, the description carries the return-value burden and does so by naming each metric and its scale. Cost, response format, and sibling routing are all covered, leaving nothing an agent needs before invoking it.

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 coverage is 100% and the schema itself fully explains the symbol-vs-name distinction and the optional type disambiguation, including the both-catalogues fallback. The description adds only "a single crypto or US stock" and does not restate the dual-listing behavior, so the schema does the heavy lifting — 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?

States a specific verb and resource ("ONE named instrument, in full") and enumerates exactly what it returns: Martingale Score, Startingale reading, breakdown, sequence structure, exchange availability. It is clearly differentiated from search_instruments, which is named explicitly.

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?

Explicit when-to-use ("when you already know the symbol") and when-to-use-the-other ("use search_instruments to find symbols"). It also resolves the practical batching question by saying walking a handful of known symbols one by one is acceptable.

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