Skip to main content
Glama

Tradingale-mcp

by com.tradingale
OverviewDiscussionsAdmin

list_top_stocks

Read-only

A RANKED LIST OF US STOCKS, sized by you: choose how many (1-20) and an optional minimum Startingale. Use this when those two are the ONLY conditions; anything else (a round count or a minimum Martingale Score) needs search_instruments. For a fixed top 5 with no arguments, use stock_overview. Answers in formatted text. Costs 3 units of the monthly quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many to return, highest Martingale Score first. 1-20, default 10.
min_startingaleNoKeep only entries at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which ranks them. 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. Changed2 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 entries at or above this Startingale reading — how well the CURRENT price sits versus the structure, unlike the Martingale Score which ranks them. 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 entries at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which ranks them. Scale 0-5: above 4.5 reads Strong, above 3.75 Favorable, above 3.25 Moderate, below that Misaligned. Default: 0 (no filter)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results. Default: 10, Max: 20"New value: +"How many to return, best Martingale Score first. 1-20, default 10."
    • changedInput schema / properties / min_startingale / description
      Previous value: -"Minimum Startingale to include. Default: 0"New value: +"Keep only entries at or above this Startingale reading — how well the CURRENT price sits versus the structure, unlike the Martingale Score which ranks them. Scale 0-5: above 4.5 reads Strong, above 3.75 Favorable, above 3.25 Moderate, below that Misaligned. Default: 0 (no filter)."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds behavioral context beyond the annotations: 'Answers in formatted text' discloses the output format, and 'Costs 3 units of the monthly quota' discloses quota impact. These add value beyond the structured annotation fields, though the exact output structure is not detailed.

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 three sentences: the first states purpose, the second provides usage routing, and the third discloses output format and cost. It is front-loaded with the core purpose and contains no filler or redundant words. Every sentence 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?

For a tool with two optional parameters and no output schema, the description covers all essential operational aspects: the resource (US stocks), the two accepted conditions, routing to alternatives, output format ('formatted text'), and quota cost. The title and schema provide the ranking criterion and parameter details, so an agent has sufficient information to invoke the tool correctly.

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%, with both `limit` and `min_startingale` fully described in the schema (including defaults, ranges, and meaning). The tool description merely echoes the parameter concepts ('choose how many (1-20) and an optional minimum Startingale') without adding new semantic detail, so the baseline score of 3 applies.

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 opens with 'A RANKED LIST OF US STOCKS' – a specific verb and resource – and immediately states the user-controlled sizing ('choose how many (1-20) and an optional minimum Startingale'). It explicitly differentiates from search_instruments and stock_overview, so an agent can distinguish this tool from its siblings even without inspecting schemas.

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?

The description states exactly when to use this tool: 'Use this when those two are the ONLY conditions.' It names the excluded conditions (a round count or a minimum Martingale Score) and directs the agent to search_instruments, and it recommends stock_overview for a fixed top 5 with no arguments. This is explicit when-to-use and when-not-to-use 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