Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

insider_sector_pulse

Read-onlyIdempotent

Sector-level insider buy/sell flow — which SIC sectors are seeing net insider buying vs selling over a window. Per sector: n_issuers_bought / n_issuers_sold / n_issuers_active, n_buyers / n_sellers, buy_usd / sell_usd, net_discretionary_usd, pct_issuers_with_buying. Backed by 11.7M Form 4/5 transaction lines (incl. derivative) from ~4.6M filings. Pre-computed for the standard windows (30/90/180/365 days) at 4-digit SIC; custom windows, historical as_of and coarser rollups run a live PIT query (~0.1-0.2s).

rollup: sic (4-digit industry, default), major_group (2-digit SIC, e.g. 28 Chemicals incl. Pharma, 73 Business Services incl. Software, 60 Banks) or division (letter A-J: Mining, Manufacturing, Finance, Services...). sort by net_discretionary (default), buy_usd, sell_usd or pct_buying; order desc (default) or asc — asc on net_discretionary puts the heaviest NET SELLING sectors first. Paginate with offset/limit; total_sectors is the full count and totals sums buy/sell/net USD and issuer counts across ALL sectors (not just the page). n_buyers/n_sellers are per-sector distinct insiders and are not summed into totals (one insider can sit at issuers in several sectors).

Grouped on the SIC code with canonical sector labels; aggregates the price-sanitized value_usd; PIT-honest on filing_date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "insider_sector_pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNonet_discretionary
as_ofNoPIT cutoff YYYY-MM-DD. Default today (only today uses the pre-computed table).
limitNoDefault 30, max 100.
orderNodesc (default) = largest first; asc on net_discretionary = biggest net sellers first.desc
offsetNoRows to skip for pagination. Default 0.
rollupNoGrouping level: 4-digit SIC (default), 2-digit SIC major group, or SIC division letter.sic
window_daysNo30/90/180/365 hit the fast pre-computed table (rollup=sic only); other values run live. Default 90.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, yet the description adds substantial context beyond them: data provenance (11.7M Form 4/5 transaction lines from ~4.6M filings), the pre-computed vs. live PIT query split with latency estimates, the fact that `totals` sums across ALL sectors rather than the current page, and that `n_buyers`/`n_sellers` are not additive. It also discloses that aggregates use a price-sanitized `value_usd` and are PIT-honest on `filing_date` — exactly the kind of caveat an agent needs to interpret results correctly.

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?

The description is front-loaded with the core purpose, then systematically covers metrics, data source, performance mode, parameter behavior, and aggregation caveats. It is dense but every paragraph earns its place; the only minor waste is repeating the `order`/`asc` semantics already spelled out in the schema.

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?

With no output schema, the description carries the full burden of explaining return values, and it does so thoroughly: it lists every per-sector field, explains `total_sectors` vs. `totals` semantics, and warns that insider counts are not summable across sectors. Combined with the latency and provenance context, an agent has everything needed to call and interpret this tool without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the schema already documents most parameters, but the description adds meaning beyond it: concrete examples of `major_group` rollups ('28 Chemicals incl. Pharma, 73 Business Services incl. Software, 60 Banks'), the A–J division letters, and the clarification that ascending `net_discretionary` surfaces the heaviest net-selling sectors. Some overlap exists (the order semantics and window behavior are also in the schema), but the rollup examples and pagination/totals semantics are genuine additions.

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 opens with a precise verb-and-resource statement: 'Sector-level insider buy/sell flow — which SIC sectors are seeing net insider buying vs selling over a window.' It then enumerates every returned metric, making the tool's output scope unmistakable. It stops short of explicitly naming a sibling (e.g., insider_flow or sector_detail) as the alternative, so differentiation is implied by the scope rather than stated.

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?

The description gives useful operational context — standard 30/90/180/365-day windows at 4-digit SIC hit the pre-computed table while custom windows, historical `as_of`, and coarser rollups run a live PIT query — which implicitly guides parameter choice. However, it never states when an agent should pick this tool over siblings like `sector_detail` or `insider_flow`; usage is inferable but not directed.

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