Fintel Discovery — Financial Intelligence for AI Agents

Get Dividends & Stock Splits

GetDividendsAndSplits

Read-onlyIdempotent

    Fetch the full history of cash dividends, stock splits, and combined
    corporate actions for a ticker. Returns date, amount/ratio for each event.

    Use this tool when:
    - You need dividend history or yield calculation inputs
    - You are researching dividend growth over time
    - You want to verify stock split history for return calculations

    Source: Yahoo Finance via yfinance. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark the tool readOnly, idempotent, and non-destructive. The description adds useful behavioral context beyond those flags: it identifies Yahoo Finance/yfinance as the source, states that no API key is required, and clarifies that the result is a full event history with date and amount/ratio. It does not discuss data freshness or rate limits, but for a read-only fetch the disclosure is adequate.

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?

The description is front-loaded with the core action and return shape, followed by a compact three-bullet usage list and a source line. Every section earns its place, and there is no redundant restating of the title or schema.

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?

Given the output schema exists and the annotations cover the safety profile, the description supplies the essential selection and invocation context: what data is returned, when to use it, the source, and auth requirements. It is not missing anything critical, though it could briefly mention limitations such as data being from Yahoo Finance rather than an official exchange source.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported at 0%, so the description carries the burden of explaining parameters, but it only loosely hints at them with 'for a ticker' and 'full history.' It does not explain the period options, the symbol requirement, or the many nested fields inside the params object. The input schema itself has some property descriptions, but the description adds little independent parameter guidance.

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?

The description opens with a specific verb-resource statement: 'Fetch the full history of cash dividends, stock splits, and combined corporate actions for a ticker.' It also names the returned fields (date, amount/ratio), so an agent can distinguish this from price, financial, or filing tools even without opening the schema.

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

Usage Guidelines4/5

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

The description provides a concrete 'Use this tool when' list covering dividend history, yield inputs, dividend growth research, and split verification. It does not explicitly state when not to use it or name alternative tools, but the guidance is clear enough for selection in most cases.

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

All Fintel Discovery — Financial Intelligence for AI Agents tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools target a distinct resource and action, with clear separation between search and detail tools (e.g., SearchIAPDFirm vs GetIAPDFirmDetail, SearchBrokerCheck vs GetBrokerCheckDetail). A few pairs like SearchBrokerCheck and SearchBrokerCheckFirm could cause momentary confusion, but descriptions clarify individual vs firm scope.

Naming Consistency4/5

The dominant pattern is consistent: Search* for discovery, Get* for retrieval, with CamelCase throughout. Minor deviations like LookupTicker and MapInstrumentIds introduce different verbs, and SearchBrokerCheck does not explicitly signal 'individual' unlike SearchBrokerCheckFirm, but the overall convention remains predictable.

Tool Count2/5

With 32 tools, the surface is quite heavy and exceeds the 25+ threshold for 'too many.' While the financial intelligence domain is broad, several search/detail pairs and overlapping data-source tools could be consolidated to reduce cognitive load for agents.

Completeness4/5

The toolset covers major workflows well: 13F holdings, fund fee comparison, advisor due diligence, macro data, price history, options, and identifier mapping. Minor gaps exist, such as no standalone real-time quote tool, no news/sentiment data, and no direct CUSIP-to-company-name search, but these are workable around.

Resources

Need Help?