Skip to main content
Glama
alpacahq

alpaca-mcp-server

Official
by alpacahq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_corporate_actions

Retrieve corporate action announcements by date, symbol, or type to get dividends, splits, mergers, and more for informed investment decisions.

Instructions

Retrieves and formats corporate action announcements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoThe inclusive end of the interval. The corporate actions are sorted by their `process_date`. Format: YYYY-MM-DD. Default: current day.
idsNoA comma-separated list of corporate action IDs. This parameter is mutually exclusive with all other filters (symbols, types, start, end, region, data_quality).
sortNoSort data in ascending or descending order.
limitNoMaximum number of corporate actions to return in a response. The limit applies to the total number of data points, not the count per symbol! Use `next_page_token` to fetch the next set of corporate actions.
startNoThe inclusive start of the interval. The corporate actions are sorted by their `process_date`. Format: YYYY-MM-DD. Default: current day.
typesNoA comma-separated list of types. If not provided, search all types. The following types are supported: - reverse_split - forward_split - unit_split - cash_dividend - stock_dividend - spin_off - cash_merger - stock_merger - stock_and_cash_merger - redemption - name_change - worthless_removal - rights_distribution - partial_call - reorganization
cusipsNoA comma-separated list of CUSIPs.
regionNoThe region to filter corporate actions by. - `us`: only US corporate actions - `non_us`: only non-US corporate actions - `all`: both US and non-US corporate actions us
symbolsNoA comma-separated list of symbols.
page_tokenNoThe pagination token from which to continue. The value to pass here is returned in specific requests when more data is available, usually because of a response result limit.
data_qualityNoControls which corporate actions are returned based on data quality. - `complete` (default): exclude corporate actions that are still missing required fields (for example, ex-date or CUSIP/ISIN) and have not yet been processed. Already-processed corporate actions are always included, even if they would otherwise be considered incomplete. - `all`: return matching corporate actions regardless of field completeness. complete

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.3.2
    • addedInput schema / properties / data_quality
      Added value: +{
+  "default": "complete",
+  "description": "Controls which corporate actions are returned based on data quality.\n\n- `complete` (default): exclude corporate actions that are still missing required\n  fields (for example, ex-date or CUSIP/ISIN) and have not yet been processed.\n  Already-processed corporate actions are always included, even if they would\n  otherwise be considered incomplete.\n- `all`: return matching corporate actions regardless of field completeness.\n",
+  "enum": [
+    "complete",
+    "all"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / ids / description
      Previous value: -"A comma-separated list of corporate action IDs. This parameter is mutually exclusive with all other filters (symbols, types, start, end).\n"New value: +"A comma-separated list of corporate action IDs. This parameter is mutually exclusive with all other filters (symbols, types, start, end, region, data_quality).\n"
    • addedInput schema / properties / region
      Added value: +{
+  "default": "us",
+  "description": "The region to filter corporate actions by.\n\n- `us`: only US corporate actions\n- `non_us`: only non-US corporate actions\n- `all`: both US and non-US corporate actions\n",
+  "enum": [
+    "us",
+    "non_us",
+    "all"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / sort / allOf
      Added value: +[
+  {
+    "default": "asc",
+    "description": "Sort data in ascending or descending order.",
+    "enum": [
+      "asc",
+      "desc"
+    ],
+    "type": "string"
+  }
+]
    • removedInput schema / properties / sort / default
      Removed value: -"asc"
    • removedInput schema / properties / sort / enum
      Removed value: -[
-  "asc",
-  "desc"
-]
    • removedInput schema / properties / sort / x-go-name
      Removed value: -"TypeSort"
    • changedInput schema / properties / types / description
      Previous value: -"A comma-separated list of types. If not provided, search all types.\n\nThe following types are supported:\n  - reverse_split\n  - forward_split\n  - unit_split\n  - cash_dividend\n  - stock_dividend\n  - spin_off\n  - cash_merger\n  - stock_merger\n  - stock_and_cash_merger\n  - redemption\n  - name_change\n  - worthless_removal\n  - rights_distribution\n"New value: +"A comma-separated list of types. If not provided, search all types.\n\nThe following types are supported:\n  - reverse_split\n  - forward_split\n  - unit_split\n  - cash_dividend\n  - stock_dividend\n  - spin_off\n  - cash_merger\n  - stock_merger\n  - stock_and_cash_merger\n  - redemption\n  - name_change\n  - worthless_removal\n  - rights_distribution\n  - partial_call\n  - reorganization\n"
  2. Addedv2.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Retrieves and formats' and does not mention sorting by process_date, pagination, region defaults, data quality filtering, or that this is a read-only operation. The description adds minimal context beyond the tool's name.

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

Conciseness3/5

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

The description is a single short sentence with no wasted words. However, the brevity comes at the cost of useful context, and the sentence does little more than restate the tool's purpose as implied by its name.

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

Completeness2/5

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

This tool has 11 parameters, no annotations, and several similarly named siblings. A one-sentence description is insufficient to guide correct selection and invocation. While the output schema and input schema provide structural detail, the description fails to explain how this tool fits among related corporate action endpoints.

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 each parameter is already documented in the input schema. The description itself adds no parameter-level meaning, but the high schema coverage means the baseline of 3 is 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?

The description states a specific verb and resource: 'Retrieves and formats corporate action announcements.' This clearly conveys the core function. However, it does not distinguish this tool from the similarly named siblings such as get_corporate_action_announcement and get_corporate_action_announcements, leaving ambiguity about which tool to select.

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?

The description provides no guidance on when to use this tool versus alternatives like get_corporate_action_announcement or get_corporate_action_announcements. It also does not mention important selection behaviors such as the mutual exclusivity of the 'ids' parameter or when to prefer this endpoint over related corporate action tools.

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