Skip to main content
Glama

AINDEX

US stocks moving most today

stock_movers
Read-only

US stocks over $2bn by today's gain, loss or volume, with price, move, volume against its average, market cap and P/E, and the Robinhood token's address when there is one.

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": "stock_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNogainers
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description does add genuinely useful behavior beyond them: a $2bn size/liquidity floor on the universe, the specific output fields, and the conditional presence of a Robinhood token address. It says nothing about ordering, cutoff semantics, or how 'active' is defined relative to volume vs. average volume.

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?

A single front-loaded sentence with no filler; the trailing field list is dense but every item is information an agent would otherwise have to guess. Slightly list-heavy, but nothing is wasted.

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?

With no output schema, the description correctly shoulders the burden by enumerating returned fields and the conditional token address. For a two-parameter screening tool that is nearly sufficient, with the only real omission being result-size and ordering semantics.

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 0%, so the description must carry meaning. It partially does: 'gain, loss or volume' maps onto the gainers/losers/active enum, which compensates for the largest gap. The count parameter (default 15, range 5-50) is entirely unaddressed, leaving the description silent on result-size behavior.

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 names a specific resource (US stocks) and screen (largest gain, loss or volume today), plus the fields returned, so an agent knows exactly what it gets. It does not differentiate itself from lookalike siblings such as market_today or get_stock_quotes, which keeps it out of the top band.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'today's gain, loss or volume' only implies the use case of scanning today's biggest movers.

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.

Resources