Skip to main content
Glama
ikop32-code

EDGAR Alert MCP Server

by ikop32-code

Get 12-week insider capital flow by industry

edgaralert_get_industry_capital_flow
Read-onlyIdempotent

Track 12-week rolling insider capital flow across Fama-French 48 industries to identify sustained sector rotation and insider buying or selling trends over the past quarter.

Instructions

Returns 12-week rolling insider capital flow (insider buy value minus sell value) for the top 6 most active FF48 industry groups by absolute net insider score. Each row contains weekStartDate, weekEndDate, ff48Code, ff48Description, sectorCode, sectorName, buyValue, sellValue, and netCapitalFlow. Industries are grouped using the Fama-French 48 classification (e.g. 'Pharmaceutical Products', 'Computers', 'Banking') nested under 11 GICS-like sectors (e.g. 'Health Care', 'Technology', 'Financials'). Use this to identify sustained sector rotation — which industries insiders have been consistently buying into or selling out of over the past quarter, not just the latest week. Complements edgaralert_get_weekly_insights (single week snapshot) with multi-week trend data. Good for questions like: 'which industries have had sustained insider buying over the past 3 months?' or 'is the tech selloff concentrated in semiconductors or broad across the sector?'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds value by explaining the rolling 12-week window, the selection criteria (top 6 by absolute net insider score), and the grouping (FF48 classification nested under GICS-like sectors). No contradictions with annotations.

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 well-structured, front-loading the main output and purpose. It is a bit lengthy but every sentence adds value, providing output fields, classification details, use cases, and sibling comparison. Could be slightly more concise, but overall efficient.

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 and zero parameters, the description comprehensively covers all necessary context: output fields, data grouping (FF48 under sectors), usage context (sustained sector rotation), and comparison to sibling tools. It fully enables correct tool invocation.

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?

The tool has zero parameters and schema coverage is 100%. According to the rules, 0 params defaults to baseline 4. The description does not need to add parameter semantics since there are none.

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?

The description clearly states the tool returns '12-week rolling insider capital flow' for the top 6 most active FF48 industry groups. It lists the specific fields (weekStartDate, weekEndDate, etc.). It explicitly distinguishes from sibling edgaralert_get_weekly_insights by noting this provides multi-week trend data versus a single-week snapshot.

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

Usage Guidelines5/5

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

The description provides explicit guidance: use this to identify sustained sector rotation, complements the weekly insights tool, and gives example questions like 'which industries have had sustained insider buying over the past 3 months?'. This clearly indicates when to use this tool vs alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ikop32-code/edgaralert-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server