Skip to main content
Glama
Sign In
MCP Yahoo Finance

MCP Yahoo Finance

by maxscheijen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_upcoming_dividends

Retrieve upcoming dividend dates and rates for a stock symbol from Yahoo Finance when available.

Instructions

Get upcoming dividend dates and rates when Yahoo provides them.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_upcoming_dividends"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock symbol in Yahoo Finance format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It hints that results may be absent ('when Yahoo provides them'), which is useful, but never confirms this is a read-only lookup, nor mentions auth, rate limits, or what an empty response means.

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?

A single front-loaded sentence with no filler. The availability clause is compact and relevant, though the sentence is sparse enough that it could have carried one more clarifying clause at no cost.

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?

For a simple one-parameter read tool with no output schema, the description covers the essentials (what data and the possibility of absence). It omits return shape details and any indication of how rates are represented, leaving modest 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% for the single 'symbol' parameter, so the schema already defines format expectations. The description adds no syntax or format detail beyond that, making the baseline 3 appropriate.

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?

States a specific verb ('Get') and resource ('upcoming dividend dates and rates'), which implicitly distinguishes it from the sibling get_dividends (presumably historical). However, it never explicitly names that sibling or draws the boundary, 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 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 versus get_dividends or get_earning_dates, and no prerequisites stated. The clause 'when Yahoo provides them' is an availability caveat, not usage guidance.

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

Deploy Server

Other Tools