Skip to main content
Glama
yyordanov-tradu

stock-scanner-mcp

tradingview_top_losers

Read-only

Retrieve top losing stocks today by percentage change on specified exchanges, filtered by market cap over $100M and excluding OTC penny stocks.

Instructions

Get today's top losing stocks by percentage change on a given exchange. Defaults to major US exchanges (NYSE, NASDAQ, AMEX) with market cap > $100M. OTC penny stocks excluded by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exchangeNoExchange (default: all US)
include_otcNoWhether to include OTC penny stocks (default: false)
limitNoMax results (default 20)
Behavior4/5

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

Annotations already indicate read-only behavior. The description adds value by detailing default filtering criteria (market cap, OTC exclusion) and real-time nature. No mention of rate limits or pagination, but not critical for this tool.

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?

Two sentences with no filler. The purpose is front-loaded in the first sentence, and defaults are provided in the second. Efficient and clear.

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?

The description covers purpose, defaults, and exclusions. For a simple list tool with no output schema, this is sufficient. Could mention sorting order, but not essential.

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

Parameters4/5

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

Schema descriptions cover all parameters (100% coverage). The description adds context about default exchanges and market cap threshold, which enhances understanding 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?

The description clearly states the tool retrieves today's top losing stocks by percentage change on a given exchange. It specifies defaults (major US exchanges, market cap > $100M) and distinguishes from sibling tools like tradingview_top_gainers.

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

Usage Guidelines4/5

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

The description implies usage context (finding today's top losers) but does not explicitly mention alternatives or when not to use. The sibling list and tool name provide some differentiation, but explicit guidance would improve clarity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yyordanov-tradu/stock-scanner-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server