Skip to main content
Glama
Snapstock MCP Server

Snapstock MCP Server

by sorndotdev

List tickers below a score

list_below_threshold
Read-only

Screen dividend payers with safety scores below a chosen threshold, sorted weakest first, to identify elevated dividend-cut risk.

Instructions

List dividend payers scoring below a safety-score threshold, sorted from weakest upward. Useful for screening for elevated dividend-cut risk. Dataset snapshot: 2026-11-15.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return. Default 25, maximum 100.
sectorNoOptional exact sector filter, for example Utilities.
maxScoreNoReturn tickers scoring strictly below this value. Default 4.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 known. The description adds real context beyond that: results come sorted weakest-first, and the data is a snapshot dated 2026-11-15, which tells the agent about staleness. Return fields and whether the list is paginated are not described.

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 plus a short snapshot fragment; scope and ordering come first, the use case second. No wording 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?

For a simple read-only filter tool with full schema coverage and no output schema, the description covers purpose, ordering, staleness, and use case. The only gap is what each returned row contains, which is minor given the tool's simplicity.

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 100%, so the schema already documents limit, sector, and maxScore completely, including the strictly-below semantics and defaults. The description adds nothing about the parameters themselves, 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 gives a specific verb and resource ('List dividend payers scoring below a safety-score threshold') plus the sort direction, which clearly separates it from single-ticker lookups like get_ticker_score. It does not name a sibling explicitly, so it stops short of a 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?

'Useful for screening for elevated dividend-cut risk' states the concrete context in which to reach for this tool over a per-ticker score lookup. It gives no explicit exclusions or named alternatives, so the guidance is clear but not complete.

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