Skip to main content
Glama

market_most_actives

Screen for the most actively traded equities. Retrieve a list of top stocks by trading activity with an optional limit.

Instructions

Current most-active equity screener.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

No annotations are present, so the description carries the full burden. It only says 'Current most-active equity screener' without explaining what 'most active' means (volume, price change?), whether it includes ETFs, or any limitations. This is woefully insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but under-specification is not conciseness. It's a single noun phrase that provides no actionable content, so the size doesn't serve the agent well.

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?

Given the tool is simple (one optional integer param, output schema exists), a basic description might suffice, but this one misses critical context. The sibling list includes 'market_movers', which likely overlaps significantly, and no differentiation or additional details are provided.

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

Parameters1/5

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

The single parameter 'limit' has no schema description (0% coverage) and the description doesn't mention it at all. The agent is left to guess how limit behaves, what its range might be, or its effect on results.

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

Purpose3/5

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

The description names a resource ('equity screener') and a temporal scope ('current most-active'), but doesn't use an explicit verb like 'lists' or 'returns', and doesn't distinguish from sibling tools like market_movers. It's more than a tautology but still vague.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No mention of use cases, prerequisites, or exclusions, so the agent gets no help deciding between this and e.g. market_movers or market_snapshot.

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/ryanrodrigues25200525-svg/tradingcli'

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