Skip to main content
Glama
bartest5

Alpaca MCP Server

by bartest5

get_corporate_actions

Retrieve corporate action announcements such as dividends, splits, and mergers, filtered by symbol, type, date range, or CUSIP. Get formatted data sorted by process date for analysis.

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).
sortNoSort data in ascending or descending order.asc
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

The description implies a non-destructive read operation ('retrieves') and mentions output formatting, but it does not disclose behaviors such as default date ranges, sorting, pagination, or any potential side effects. With no annotations provided, the description carries the burden but only partially addresses it.

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 a single concise sentence that directly states the tool's purpose without any wasted words. It is appropriately front-loaded and easy to parse.

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?

The tool has 10 optional parameters and a complex query interface, yet the description offers no overview or usage context. It does not explain how this tool fits with siblings or what scenarios it is designed for, leaving the agent to rely entirely on the schema. The output schema exists, so return values are covered, but the description is still inadequate for the tool's complexity.

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?

The input schema provides 100% coverage of parameter descriptions, so the description adds no additional semantic value. The baseline of 3 is appropriate since the schema already documents all parameters.

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 clearly states the tool retrieves and formats corporate action announcements, using a specific verb and resource. However, it does not differentiate from the sibling tool get_corporate_action_announcements, which likely serves a similar purpose, so it lacks distinctiveness.

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, nor any exclusions or prerequisites. It simply states what it does without contextual usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bartest5/alpacahq_alpaca-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server