Skip to main content
Glama
Snapstock MCP Server

Snapstock MCP Server

by sorndotdev

Search dividend payers

search_tickers
Read-only

Search and screen dividend stocks by ticker, company name, sector, safety score, and minimum yield, returning up to 100 matches with score, yield, streak, and red-flag count.

Instructions

Search or screen the Snapstock dataset by ticker, company name, sector, score range, and minimum yield. Returns up to 100 matches with score, yield, streak, and red-flag count. 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": "search_tickers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return. Default 20, maximum 100.
queryNoTicker or company-name fragment, for example 'yield', 'Realty', or 'KO'.
sectorNoExact sector name, for example Financial Services, Utilities, or Real Estate.
maxScoreNoMaximum safety score (0-10).
minScoreNoMinimum safety score (0-10).
minYieldNoMinimum trailing dividend yield in percent, for example 4 for 4%.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 safety is covered; the description adds genuinely new context by naming the returned fields (score, yield, streak, red-flag count), the result ceiling of 100, and the dataset snapshot date of 2026-11-15, which tells the agent the data can be stale. It stops short of describing ordering, pagination, or empty-result behavior.

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 with no filler: the capability and its filters come first, followed by return shape and snapshot date. Every clause carries information an agent can act on.

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 six-parameter, read-only search tool with no output schema, the definition covers what is queried and roughly what comes back, plus dataset currency. It omits the default limit of 20, result ordering, and how 'query' matching works (fragment vs exact), which are the remaining gaps for correct invocation.

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 all six parameters including limit are already documented in the schema. The description restates the filter facets and only adds the implicit mapping of 'up to 100 matches' to the limit cap, which is a marginal gain over the structured data.

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?

Uses a specific verb ('search or screen') against a named resource (the Snapstock dataset) and enumerates the filterable facets: ticker, company name, sector, score range, minimum yield. This is clearly a multi-result query tool, but it does not explicitly contrast itself with single-lookup siblings such as get_ticker_score or list_below_threshold, so differentiation is left to inference.

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

Usage Guidelines3/5

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

'Search or screen' implies use when you want a filtered set of matches rather than a known single ticker, and the 100-result cap hints at bulk exploration. However, no explicit when-to-use/when-not guidance or named alternative is given, so the agent must infer that per-ticker details belong to sibling tools.

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