Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Chart Events (filing-native markers: earnings/dividend/split/insider/stake/campaign/formd/debt/contract/auditor)

chart_events
Read-onlyIdempotent

Filing-native event markers for one company, meant to be plotted on a price chart: earnings (beat/miss), dividends, splits, insider transactions (open-market buy/sell, 10b5-1 plan — grouped one marker per day+kind), 13D/13G ownership stakes, activist-campaign events, new Form D private offerings, debt obligations, material contracts (commercial/M&A/capital-markets/real-estate/credit only — employment and equity-award contracts are excluded as chart noise), and auditor changes.

Every marker carries accession (not a SEC.gov URL) so a caller opens the actual filing, plus filing_url; insider markers (one per day+kind) carry accessions (the Form 4s grouped into the marker, max 10). tone is +1 (beat/buy) or -1 (miss/sell) where applicable, null otherwise. Contracts are capped at 150 by dollar value and insider markers at 150 keeping every buy first — both per Console's own noise-control rules, not an arbitrary truncation.

Each lane degrades independently: if one source is unavailable or empty the rest of the response is unaffected — check warnings for any lane that failed, don't assume a missing lane means 'no events.'

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": {
      "ticker_or_cik": "<ticker_or_cik>"
    },
    "name": "chart_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD. Default: today.
startNoYYYY-MM-DD. Default: 2 years ago.
typesNoRestrict to these event lanes. Default: all.
ticker_or_cikYesTicker or CIK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/non-destructive/closed-world; the description adds substantially more: `accession` is an ID not a URL, insider markers carry grouped `accessions` (max 10), `tone` is +1/-1/null, and contracts/insider lanes are capped at 150 by explicit noise-control rules. Crucially it discloses per-lane independent degradation — a genuine behavioral trait an agent cannot infer from structured fields.

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 short paragraphs, capability first, then return shape, then failure semantics — front-loaded and mostly waste-free. The first sentence is an extremely dense run-on list of lanes that is harder to parse than necessary, which keeps it just short of a 5.

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

Completeness5/5

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

No output schema exists, and the description fills that gap by describing marker fields (`accession`, `filing_url`, grouped `accessions`, `tone`), truncation behavior, and `warnings` for failed lanes. For a 4-param read tool with rich annotations, an agent has everything needed to call it and interpret the result correctly.

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 `ticker_or_cik`, `start`/`end` defaults and the lane enum are already fully documented in the schema. The description adds meaning about lane semantics (what each type yields, why some are excluded) but nothing per-parameter beyond the schema, so the baseline 3 applies.

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 verb+resource (filing-native event markers for one company) and enumerates all ten lanes plus what the markers are for (plotting on a price chart). The parenthetical scope limits (contracts exclude employment/equity-award, insider markers grouped per day+kind) let an agent distinguish this from sibling event/insider tools without opening the schema.

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

Usage Guidelines4/5

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

Use context is clear and front-loaded: "meant to be plotted on a price chart," i.e. a consolidated marker lane rather than per-filing lookup. It also tells the caller how to react to gaps ("check `warnings`... don't assume a missing lane means 'no events'"). It stops short of naming when to prefer a dedicated sibling (e.g. a single-lane insider or activism tool) over this aggregate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources