alpaca-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

get_corporate_actions

Retrieve and format corporate action announcements such as splits, dividends, and mergers by date, symbol, type, or region.

Instructions

Retrieves and formats corporate action announcements.

Input Schema

Name	Required	Description	Default
`end`	No	The inclusive end of the interval. The corporate actions are sorted by their `process_date`. Format: YYYY-MM-DD. Default: current day.
`ids`	No	A comma-separated list of corporate action IDs. This parameter is mutually exclusive with all other filters (symbols, types, start, end, region, data_quality).
`sort`	No	Sort data in ascending or descending order.
`limit`	No	Maximum 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.
`start`	No	The inclusive start of the interval. The corporate actions are sorted by their `process_date`. Format: YYYY-MM-DD. Default: current day.
`types`	No	A 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 - capital_gains_distribution
`cusips`	No	A comma-separated list of CUSIPs.
`region`	No	The 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
`symbols`	No	A comma-separated list of symbols.
`page_token`	No	The 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_quality`	No	Controls 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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.4.0Oct 17, 2026

changedInput schema / properties / sort / allOf

Previous value: -[
-  {
-    "default": "asc",
-    "description": "Sort data in ascending or descending order.",
-    "enum": [
-      "asc",
-      "desc"
-    ],
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "default": "asc",
+    "description": "Sort data in ascending or descending order.",
+    "enum": [
+      "asc",
+      "desc"
+    ],
+    "type": "string"
+  }
+]

removedInput schema / properties / sort / type
```
Removed value: -"string"
```

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  - partial_call\n  - reorganization\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  - capital_gains_distribution\n"

Changed8 schema fields changedv2.3.2Sep 18, 2026

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"

Addedv2.0.0Apr 15, 2026

TDQS

C2.9/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. 'Retrieves' weakly implies a read operation, but there is no statement about it being read-only, no mention of pagination expectations, result caps, or permission requirements, all of which matter for an 11-parameter listing tool.

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 wasted words; every word earns its place. It is efficient, though the terseness leaves the specification thin rather than verbose.

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?

For an 11-parameter tool with zero annotations and multiple same-domain siblings, the description is inadequate: it does not explain the filtering model, the default region/date behavior, or how it differs from get_corporate_action_announcements. The existing output schema relieves it of return-value explanation, but that is the only gap it is excused from.

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 already explains dates, sorting, pagination tokens, the mutually exclusive ids parameter, and the region/data_quality enums. The description adds nothing beyond that, which meets the baseline 3 for schema-driven parameter documentation.

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 (retrieves) and resource (corporate action announcements), so an agent knows the general operation. However, it offers no differentiation from the near-identically named siblings get_corporate_action_announcements and get_corporate_action_announcement, and the word 'formats' is vague about what 'formatting' entails.

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?

There is no when-to-use guidance, no exclusions, and no pointer to the singular/plural sibling tools that appear to cover the same domain. The agent must infer usage entirely from the name and schema.

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

Deploy Server