Skip to main content
Glama

StocksScores

Highest scoring stocks

top_scores
Read-only

The best-scoring symbols in the universe right now, highest first. Ranks only investable names — excludes symbols under $5, under $1B market cap, or with a risk grade above 7. Use screen_stocks to search without that ranking cut.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 10, max 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that by disclosing the investability filter (price < $5, market cap < $1B, risk grade > 7), which explains why results may be narrower than an agent expects. It stops short of describing return fields or ordering ties, keeping it at 4 rather than 5.

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, front-loaded with what the tool returns, followed by the sibling routing. Every clause carries information — the exclusion criteria in particular earn their space.

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?

For a one-param, read-only ranking tool this is nearly complete: it explains scope, ordering, exclusions, and the alternative. The minor gap is that it never hints at what a returned row contains (symbol, score, grade), though with no output schema that is a small omission.

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?

There is a single optional 'limit' parameter whose schema description is already complete (default 10, max 200). The description adds no extra meaning about it, so with 100% schema coverage the baseline 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?

States a specific resource ('the best-scoring symbols in the universe') plus the ordering ('highest first') and the eligibility rule, which immediately separates it from a general screener. An agent can tell what it returns without opening the schema.

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?

Explicitly names the alternative and the condition that selects it: use screen_stocks when you want to 'search without that ranking cut.' The when-to-use-this and when-to-use-the-sibling split is fully spelled out.

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.