Skip to main content
Glama

Stock Trends Market Intelligence

Get Top Stock Trends Screener Results

stocktrends_get_screener_top
Read-only

Purchase the API-authored ranked screener output with an x402 payment authorization. Results are research context, not a buy or sell recommendation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stocktrends_get_screener_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorsi
limitNo
trendNo
min_rsiNo
exchangeNo
weekdateNo
min_mt_cntNo
min_trend_cntNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The description adds genuinely useful context beyond the annotations: the call requires an x402 payment authorization, and the output is research context rather than a recommendation. However, it resolves none of the operational questions a paid call raises (cost amount, behavior when authorization is missing or insufficient, whether a failed payment is retried or charged) and does not explain the tension between readOnlyHint=true and a spending operation, which is only partially reconciled by idempotentHint=false.

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?

Two short sentences, front-loaded with the action and its payment requirement, with the disclaimer placed second. The disclaimer is close to boilerplate but is defensible for a financial-data tool; nothing else is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, non-idempotent tool with eight undocumented parameters and no output schema, the description leaves the important gaps open: no cost or payment flow, no error behavior on authorization failure, no sense of what the ranked output contains (symbols? scores? RSI values?), and no routing guidance among the many sibling screener and indicator tools. The disclaimer and payment note are necessary but far from sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%: the schema supplies only types, enums, defaults and ranges, and the description mentions no parameter at all. Self-describing names (limit, min_rsi, weekdate) let an agent guess, but nothing documents what 'sort: mt_cnt' ranks by, how trend and weekdate interact, or whether the filters are ANDed, and the description makes no attempt to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb ('Purchase') and a concrete resource ('API-authored ranked screener output'), so an agent knows this retrieves a ranked screener result set rather than computing one. It does not, however, differentiate itself from adjacent screener/selection siblings such as stocktrends_get_selections_latest or stocktrends_get_leadership_summary_latest, leaving the agent to infer the distinction from the name alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g. an x402 wallet/authorization must be available first), and no named alternative among the 18 siblings. The purchase framing implies a cost precondition but the description never says to prefer a cheaper non-paid sibling when a paid screener snapshot is unnecessary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.