Skip to main content
Glama
Snapstock MCP Server

Snapstock MCP Server

by sorndotdev

Get dividend safety score

get_ticker_score
Read-only

Retrieve a 0–10 dividend safety score, label, component scores, streak, and yield for a US-listed dividend payer by ticker.

Instructions

Get Snapstock's 0-10 dividend safety score, label, five component scores, streak, and yield for one US-listed dividend payer. The score is a research aid, not investment advice. Dataset snapshot: 2026-11-15 (CC BY 4.0).

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_ticker_score"
  }
}

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

A4.2/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 description's job is to add context, which it does well: it discloses the dataset snapshot date (2026-11-15), the CC BY 4.0 license, and an explicit 'not investment advice' disclaimer. What it omits is failure behavior for unknown or non-dividend tickers, which is the main remaining behavioral unknown.

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 resource and payload, followed by the disclaimer and provenance. Every sentence carries distinct information — no restatement of the title or the ticker parameter.

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 correctly enumerates the returned fields, and it supplies freshness and licensing metadata an agent would otherwise lack. The only gap is what happens when the ticker isn't a dividend payer or doesn't exist, which matters for a tool whose scope is explicitly dividend payers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 baseline would be 3. The description adds genuine meaning beyond the schema by restricting the domain to 'one US-listed dividend payer', signaling that non-US listings and non-payers are out of scope for this parameter value.

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?

Names a specific verb and resource ('Get Snapstock's 0-10 dividend safety score') and enumerates exactly what comes back: label, five component scores, streak, and yield. The scope clause 'for one US-listed dividend payer' plus the enumerated payload separates it cleanly from history-oriented siblings like get_dividend_history or get_red_flags.

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?

Usage is implied rather than stated: 'for one US-listed dividend payer' tells the agent the tool is inapplicable to non-US listings or non-payers, and the 'research aid' caveat frames intent. However, it never says when to prefer this over get_dividend_history, get_red_flags, or list_below_threshold, leaving the routing decision to inference.

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