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

TableJSON Schema
NameRequiredDescriptionDefault
typeNoWhich 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.
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. 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."
  2. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "crypto",
-  "stock",
-  "commodity"
-]New value: +[
+  "crypto",
+  "stock"
+]
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context beyond that: the call costs 1 quota unit, the response is formatted text rather than JSON, and it returns a single instrument in full. These are concrete operational traits an agent needs to know.

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?

The description is four compact sentences with no wasted words. The lead sentence immediately scopes the tool's purpose and return contents, and every subsequent sentence adds distinct value: routing, output format, and cost.

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 full burden of explaining return values, and it does so by listing the exact fields returned. It also covers cost, output format, symbol-vs-name usage, and directs the agent to the correct sibling tool, making the definition complete for a simple lookup tool.

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 both parameters are already well documented: symbol includes examples and case-insensitivity, type explains its default and optimization role. The description adds no new parameter-level detail, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: it fetches ONE named instrument in full, and enumerates exactly what is returned (Martingale Score, Startingale reading, breakdown, sequence structure, exchange availability). It is clearly distinguished from search_instruments, which is for finding symbols rather than retrieving a known one.

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 says when to use it ('when you already know the symbol') and names the alternative for the other case ('use search_instruments to find symbols'). It also adds cost context, telling the agent this is the cheapest call, which directly informs selection.

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