Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Corporate action marks on the chart

price_corp_action_marks
Read-onlyIdempotent

Fetches dividends, splits, rights issues and other corporate actions for a stock symbol between two dates, returned as chart markers with timestamps, colors, labels and tooltips.

Instructions

Dividends, splits, rights and other corporate actions of one symbol between two dates, as chart markers.

Returns (Stockbit's data field): {data[{id, time (unix sec; client adds 7h/9h), color, label, tooltips}]}.

Endpoint: GET exodus /chartbit/chart/corpaction.

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>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "price_corp_action_marks"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesto
fromYesfrom
symbolYessymbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly/idempotent/non-destructive/openWorld, so the description's extra work is what matters. It does add real context beyond them: the return payload shape, the underlying endpoint, and the caveat that 'time' is unix seconds where the client applies a 7h/9h offset — a detail an agent would otherwise get wrong when displaying timestamps.

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?

Three compact segments: what it returns, the response shape, and the endpoint. Purpose is front-loaded with no filler, though the raw endpoint string is of marginal use to an agent compared with a note about coverage or pagination.

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

Completeness4/5

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

Only 3 required parameters, no output schema, and the description compensates by describing the returned data array and its fields, plus the timestamp caveat. What is missing is narrower: no mention of whether the result is complete for the range or of retention limits on historical corporate actions.

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%, but the schema descriptions are the bare words 'symbol', 'from' and 'to', so they add little on their own. The description restates the semantics ('one symbol between two dates') but does not clarify date format handling, timezone of the from/to bounds, or whether both endpoints are inclusive. Baseline 3 is warranted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (dividends, splits, rights and other corporate actions), for a single symbol, over a date range, returned as chart markers. That is concrete enough to separate it from the price_*, broker_activity_chart and financial_chart siblings, which return series rather than event markers.

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: 'as chart markers' signals this is for annotating a chart, and the symbol/date-range scoping is clear. It never states when to prefer it over price_chart or another chart tool, nor whether the date range is inclusive or bounded by listing history.

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