massive-mcp

by danielbres

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_dividends

Fetch historical and upcoming stock dividends. Filter by symbol or ex-dividend date to access payment schedules.

Instructions

Historical and upcoming dividends.

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

Input Schema

Name	Required	Description
`ticker`	No	Filter by symbol. If None, returns across all tickers.
`ex_dividend_date_gte`	No	Inclusive lower bound on ex-date ("YYYY-MM-DD").
`limit`	No	Max rows. Default 20.
`cursor`	No	Pagination cursor.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are present, so the description must bear the full burden. It fails to disclose any behavioral traits like data freshness, authorization needs, pagination behavior (cursor parameter), or whether results are sorted. This is minimal behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, front-loaded with key terms. No extraneous words, but it could benefit from a verb for structure.

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

Completeness3/5

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

Given the presence of a detailed input schema and output schema, the description provides a basic understanding. However, it lacks information on pagination, date range semantics, and the combination of parameters, leaving some gaps.

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 baseline is 3. The description does not add any meaning beyond the schema's parameter descriptions (e.g., it doesn't clarify how ticker interacts with ex_dividend_date_gte). No added value.

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 'Historical and upcoming dividends' clearly indicates the tool returns dividend data, distinguishing it from siblings like get_splits or get_financials. However, it lacks an explicit verb like 'retrieve' or 'list', making it slightly less direct.

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 guidance on when to use this tool versus alternatives, such as get_financials or get_ticker_events. No context about typical use cases or exclusions provided.

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