Skip to main content
Glama
Sign In
EDGAR Alert MCP Server

EDGAR Alert MCP Server

by ikop32-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get stock price performance around an alert

edgaralert_get_alert_price_window
Read-onlyIdempotent

Retrieve daily stock prices before and after a specific insider trading alert to backtest if the signal predicted a price move.

Instructions

Returns daily price history for the stock around the date of a specific insider trading alert, useful for backtesting whether the signal preceded a price move. Requires an alert id from edgaralert_search_alerts or edgaralert_get_latest_alerts. Requires EDGAR Alert PRO plan or higher.

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": {
      "alertId": "<alertId>"
    },
    "name": "edgaralert_get_alert_price_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo"watchlist" restricts to the user's default ticker list, "universe" (default) does not.
alertIdYesThe numeric id of the alert (from a search or latest-alerts result).
daysAfterNoDays of price history after the alert date.
daysBeforeNoDays of price history before the alert date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description consistently reinforces a safe, read-only behavior. It adds the PRO plan requirement, which is valuable behavioral context beyond annotations. 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?

Three sentences, each serving a distinct purpose: function, data source, and access requirement. Efficiently structured with no superfluous words.

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

Completeness3/5

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

For a read-only tool with robust annotations and schema, the description is largely complete. However, it lacks an explanation of the output format (e.g., fields returned, date range limits), which would be helpful since there is no output schema.

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 coverage is 100% and each parameter has a clear description. The tool description adds high-level context (e.g., 'around an alert') but no additional syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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?

Clearly states it returns daily price history for a stock around an alert date, with an explicit backtesting use case. The verb 'get' and resource 'price_window' are specific. It distinguishes from siblings by focusing on price history around alerts, contrasting with search/add/list operations.

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?

Provides clear context: useful for backtesting, requires an alert ID from specific sibling tools, and requires a PRO plan. However, it does not explicitly state when not to use it or list alternatives.

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