corp_actionFetch corporate actions—stock splits, buybacks, name changes—for a security symbol to track important company events.
Get corporate actions (splits, buybacks, name changes).
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Security symbol, e.g. "700.HK" |
| Name | Required | Description | Default |
|---|---|---|---|
| items | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.8.7Output schema / $defs / CorpActionItem / properties / descriptionAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}v0.7.1Input schema / titleRemoved value: -"SymbolParam"v0.6.0Output schema / $defs / CorpActionItem / descriptionRemoved value: -"One event in `corp_action`'s `items`.\n\nSubset of documented fields; upstream may return more."Output schema / $defs / CorpActionItem / properties / action_type / descriptionRemoved value: -"Action type (split, buyback, name change, ...)."Output schema / $defs / CorpActionItem / properties / descriptionRemoved value: -{
- "description": "Free-text description.",
- "type": [
- "string",
- "null"
- ]
-}Output schema / $defs / CorpActionItem / properties / effective_date / descriptionRemoved value: -"Effective date."Output schema / $defs / CorpActionItem / properties / ratio / descriptionRemoved value: -"Ratio (e.g. for splits)."Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved value: -"Returned by `corp_action`. Wraps an `items` array of corporate actions.\n\nSubset of documented fields; upstream may return more."Output schema / properties / items / descriptionRemoved value: -"Corporate action events."Output schema / titleRemoved value: -"CorpActionResponse"v0.5.6Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "CorpActionItem": {
+ "description": "One event in `corp_action`'s `items`.\n\nSubset of documented fields; upstream may return more.",
+ "properties": {
+ "action_type": {
+ "description": "Action type (split, buyback, name change, ...).",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "description": "Free-text description.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "effective_date": {
+ "description": "Effective date.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "ratio": {
+ "description": "Ratio (e.g. for splits).",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ }
+ },
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "description": "Returned by `corp_action`. Wraps an `items` array of corporate actions.\n\nSubset of documented fields; upstream may return more.",
+ "properties": {
+ "items": {
+ "description": "Corporate action events.",
+ "items": {
+ "$ref": "#/$defs/CorpActionItem"
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ }
+ },
+ "title": "CorpActionResponse",
+ "type": "object"
+}v0.4.5v0.4.0v0.3.2v0.3.1v0.1.12Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a few example event types but provides no extra behavioral context such as result scope, response size, or whether historical events are included.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler or redundancy. Every word contributes to conveying the tool's core function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity (one required parameter), strong annotations, and presence of an output schema, the description is sufficiently complete for an agent to understand and invoke the tool. No return-value clarification is needed because the output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'symbol' is fully described in the schema with an example ('700.HK'). Schema description coverage is 100%, so the description does not need to add much. It adds no additional parameter semantics beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool's purpose: 'Get corporate actions' with concrete examples ('splits, buybacks, name changes'). This is a specific verb + resource, but it does not explicitly distinguish itself from closely related sibling tools like dividend or capital_distribution.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives such as dividend, capital_distribution, or other corporate-event tools. The intended use is only implied by the tool name and one-line description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server