Skip to main content
Glama

Splits and dividends per share

corporate_actions
Read-onlyIdempotent

Return a company's stock splits (as reported in XBRL, with whether IEX prices across the ex-date confirm the ratio) and its dividends per share declared or paid in each fiscal period, as filed. A dividend row is a per-period total, not one payment, and has no ex-date. Every value carries the XBRL fact as proof. For split-adjusted prices call stock_prices with adjust "splits". Use it to check for a stock split before comparing per-share figures or prices across dates.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "ticker:AAPL"
    },
    "name": "corporate_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly declared or only paid dividends.
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 12, at most 400).
companyYesCompany identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.

Output Schema

NameRequiredDescriptionDefault
dataNo{ splits: { items }, dividends: { items } } from GET /v1/company/splits and /v1/company/dividends.
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description correctly spends its words on behavior the schema cannot express: dividends are per-period totals rather than single payments, they carry no ex-date, splits are cross-validated against IEX prices across the ex-date, and every value carries the underlying XBRL fact. These are exactly the interpretive caveats an agent needs to avoid misreading the output.

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?

Four sentences with no filler: resource definition first, then the critical output caveat about dividend granularity, then the data-provenance note, then the alternative route and the use case. The parentheticals are dense but each carries information an agent would otherwise have to guess.

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

Completeness5/5

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

For a read-only, fully-described 4-parameter tool with an output schema and complete annotations, the description supplies everything additional an agent needs: what the rows mean, the grain of dividend data, provenance, and a cross-tool routing hint. Nothing material is deferred to guesswork.

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 kind, as_of, limit, and company are already fully documented in the input schema. The description adds only indirect meaning — 'declared or paid' echoes the kind enum and 'as filed' gestures at the knowledge-date semantics — so this sits at the expected baseline for a fully documented schema.

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 names a specific verb and two concrete resources: 'stock splits (as reported in XBRL, with whether IEX prices across the ex-date confirm the ratio)' and 'dividends per share declared or paid in each fiscal period, as filed.' It also draws a boundary against the sibling stock_prices by pointing at the 'adjust "splits"' path, so an agent can tell this apart from a price-series call.

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?

It gives an explicit use case — 'check for a stock split before comparing per-share figures or prices across dates' — and routes the agent to stock_prices with adjust "splits" for split-adjusted prices. What it lacks is a negative case, e.g. when to prefer the sibling dividends tool or when splits data will be absent (non-SEC EU/UK issuers).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources