Skip to main content
Glama
Sign In
EDGAR Alert MCP Server

EDGAR Alert MCP Server

by ikop32-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get weekly insider trading market summary

edgaralert_get_weekly_insights
Read-onlyIdempotent

Summarize weekly insider trading activity by highlighting bullish and bearish industries and top buying and selling companies. Provides a market-wide overview to guide further research.

Instructions

Returns a market-wide weekly summary of insider trading activity: the most bullish and bearish industries by net insider signal, and the top buying/selling companies for the week. Good for broad 'what's the market doing' questions before drilling into a specific company or sector.

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": "edgaralert_get_weekly_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds value by detailing the return content (weekly summary, top industries/companies), which is beyond what annotations provide. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with key information. Every word is meaningful and no fluff. Highly concise.

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?

Given no parameters, no output schema, and simple functionality, the description fully covers what the tool does and when to use it. No gaps.

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?

There are no parameters, so the description does not need to add parameter details. Baseline of 4 is appropriate as schema coverage is 100% and the tool requires no input.

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 it returns a market-wide weekly summary of insider trading activity, specifying the exact outputs: most bullish/bearish industries and top buying/selling companies. This is specific and distinct from sibling tools that focus on individual companies or alerts.

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?

Explicitly says 'Good for broad "what's the market doing" questions before drilling into a specific company or sector.' This gives clear context on when to use this tool versus alternatives like company profile or industry capital flow 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