Skip to main content
Glama
alpacahq

alpaca-mcp-server

Official
by alpacahq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_corporate_action_announcements

Retrieve corporate action announcements (dividends, mergers, splits, spinoffs) within a 90-day date range, filtering by symbol, CUSIP, or action type to get targeted results.

Instructions

Retrieves corporate action announcements (dividends, mergers, splits, spinoffs). Use a narrow date range and filter by symbol when possible — broad queries can return very large responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cusipNoThe CUSIP of the company initiating the announcement.
sinceYesThe start (inclusive) of the date range when searching corporate action announcements. This should follow the YYYY-MM-DD format. The date range is limited to 90 days.
untilYesThe end (inclusive) of the date range when searching corporate action announcements. This should follow the YYYY-MM-DD format. The date range is limited to 90 days.
symbolNoThe symbol of the company initiating the announcement.
ca_typesYesA comma-delimited list of corporate action types.
date_typeNodeclaration_date, ex_date, record_date, or payable_date

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.3.2
    • changedInput schema / properties / ca_types / description
      Previous value: -"A comma-delimited list of Dividend, Merger, Spinoff, or Split."New value: +"A comma-delimited list of corporate action types."
    • addedInput schema / properties / ca_types / items
      Added value: +{
+  "description": "The type of corporate action.",
+  "enum": [
+    "Spinoff",
+    "Merger",
+    "Split",
+    "Reorg",
+    "Dividend"
+  ],
+  "example": "Dividend",
+  "title": "CorporateActionCaType",
+  "type": "string"
+}
    • changedInput schema / properties / ca_types / type
      Previous value: -"string"New value: +"array"
  2. Addedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It usefully discloses that broad queries can return very large responses, which is a non-obvious operational trait. It does not mention pagination, rate limits, or the 90-day date restriction, though some of this is present in the schema.

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?

Two sentences, front-loaded with the tool's purpose, followed by a pointed performance warning. Every sentence earns its place and there is no redundant filler.

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 rich input schema and presence of an output schema, the description is mostly sufficient for correct invocation. The main gap is the lack of differentiation from sibling tools like get_corporate_action_announcement and get_corporate_actions, which could leave an agent unsure if this is the right endpoint.

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 the schema fully documents all six parameters. The description adds only practical guidance around narrowing date range and filtering by symbol, but it does not add new parameter-level meaning beyond what the schema already provides.

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 states a specific verb and resource: "Retrieves corporate action announcements" with examples (dividends, mergers, splits, spinoffs). However, it does not distinguish itself from siblings like get_corporate_action_announcement (singular) or get_corporate_actions, so an agent may not know which tool to select for a given intent.

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 gives actionable usage guidance: "Use a narrow date range and filter by symbol when possible" and warns that broad queries return very large responses. It does not, however, mention when to prefer this tool over the sibling corporate action tools or state any exclusions.

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