Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Active corporate action of a symbol

corpaction_status
Read-onlyIdempotent

Check whether one or more tickers currently has an active corporate action, such as a cum date window, using Stockbit per-symbol corporate action status.

Instructions

Whether one symbol has an active corporate action now (e.g. in a cum date window).

Returns (Stockbit's data field): data: per-symbol corp-action status (shape not consumed in visible code; unknown)

Endpoint: GET exodus /corpaction/status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "corpaction_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesComma-separated tickers (symbol.join(','))

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful admission that the returned 'data' field's shape is unknown and names the underlying endpoint, but it says nothing about auth needs, rate limits, or what happens when multiple tickers are passed.

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 text is short and front-loads the core question, which is good. However, the parenthetical '(shape not consumed in visible code; unknown)' and the raw 'Endpoint: GET exodus /corpaction/status' line are implementation trivia that consume space without helping an agent decide or call.

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

Completeness3/5

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

For a one-parameter read tool with full annotation coverage and no output schema, the essentials are present. Still missing: how multi-ticker input is reflected in the response, and any notion of what 'active' means in return terms, leaving the 'one symbol' versus ticker-list ambiguity unresolved.

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 coverage is 100% and the single 'symbol' parameter is documented in the schema as comma-separated tickers, so the baseline is 3. The description contributes no parameter detail and actually creates mild tension by framing the tool as being about 'one symbol' while the schema accepts a joined ticker list.

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 concrete predicate plus resource: whether a symbol currently has an active corporate action, with an illustrative condition ('in a cum date window'). That is far more specific than the title alone and distinguishes it from calendar/category-style siblings, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer 'use this to check if a corp action is currently active for a ticker' from the cum-date example. There is no statement of when not to use it, no prerequisites, and no routing to related corp-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