Skip to main content
Glama

StocksScores

Screen or compare stocks

screen_stocks
Read-only

Filter last night’s scores across every scoreable US-listed company by score band, sector, or a list of tickers to compare side by side. Returns compact rows, highest score first, each with how many points the composite moved in about a week. The feed excludes symbols whose fundamental score is missing or built on under 40% of the fundamental weight — closed-end funds, preferred lines and pre-merger shells.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 25, max 200)
sectorNoExact sector name, e.g. Technology
symbolsNoOnly these tickers (max 50); any not in the feed come back under `missing`
maxScoreNoOnly symbols scoring at or below this (0-100)
minScoreNoOnly symbols scoring at or above this (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / symbols
      Added value: +{
      +  "description": "Only these tickers (max 50); any not in the feed come back under `missing`",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / required
      Added value: +[]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real behavioral load — and it does: return shape (compact rows), ordering (highest score first), an extra computed field (composite point move over about a week), and a precise feed exclusion rule (missing fundamental score or under 40% of fundamental weight; CEFs, preferreds, pre-merger shells). That is substantive disclosure an agent cannot get from the annotations.

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?

Three sentences, each carrying distinct payload: what it filters, what comes back, and what is excluded. Ordering is front-loaded toward the agent's decision (filter criteria) before the caveats, with no filler.

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

Completeness5/5

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

There is no output schema, but the description compensates by describing row shape, sort order, and the momentum field, plus the coverage caveat that would otherwise cause an agent to misread an empty or short result. For a 5-parameter, all-optional screening tool, nothing essential is missing.

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 coverage is 100%, so limit, sector, symbols, minScore, and maxScore are already documented, including defaults, caps, and the `missing` bucket. The description restates the filter dimensions ('score band, sector, or a list of tickers') without adding new semantics such as band conventions or interaction between min and max, so the baseline 3 applies.

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 verb and resource ('Filter last night's scores') and pins the scope precisely: every scoreable US-listed company, filtered by score band, sector, or ticker list. It never names a sibling such as top_scores or get_score_history to draw an explicit boundary, so it lands at 4 rather than 5.

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?

'to compare side by side' and the filtering dimensions make the intended use case clear: screening and head-to-head comparison. It gives no explicit when-not guidance or pointer to an alternative for, say, single-symbol deep analysis, which is why it is not a 5.

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.