Skip to main content
Glama
Snapstock MCP Server

Snapstock MCP Server

by sorndotdev

Get dividend red flags

get_red_flags
Read-only

Retrieve dividend red flags for one ticker, including five- and ten-year dividend-decline signals, earnings and free-cash-flow payout ratios, and the current score.

Instructions

List Snapstock's red flags for one ticker, including explicit five- and ten-year dividend-decline flags, earnings and free-cash-flow payout ratios, and the current score. Research aid, not investment advice. Dataset snapshot: 2026-11-15.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_red_flags"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker symbol, for example A, AAPL, KO, or JNJ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 context beyond that: the dataset snapshot date (2026-11-15) and the 'research aid, not investment advice' framing, but says nothing about freshness limits, coverage gaps, or what happens for tickers with no dividend data.

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 short sentences, front-loaded with the core action and payload, then the disclaimer and snapshot date. Nothing is redundant and the ordering puts the most decision-relevant information first.

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 usefully enumerates what comes back (decline flags, two payout ratios, current score) and pins the data vintage. That is adequate for a single-parameter read tool; only the missing sibling routing keeps it from being complete.

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% and the ticker parameter already carries example symbols, so the schema does the heavy lifting. The description's only added semantic is that the call is scoped to exactly one ticker, with no detail on symbol format or validation failures beyond what the schema states.

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 and resource ('List Snapstock's red flags for one ticker') and enumerates the payload (five-/ten-year dividend-decline flags, earnings and FCF payout ratios, current score), which clearly separates it from a plain score tool like get_ticker_score. It stops short of naming any sibling explicitly, so the differentiation is inferential.

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?

No when-to-use or when-not-to-use guidance is given. An agent must guess whether this supersedes get_dividend_history or get_ticker_score; the only scoping cue is the implied single-ticker restriction in 'for one ticker'.

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