Skip to main content
Glama
Sign In
EDGAR Alert MCP Server

EDGAR Alert MCP Server

by ikop32-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get company profile

edgaralert_get_company_profile
Read-onlyIdempotent

Retrieve a company profile including identity, market summary, fundamentals, insider trading details, and recent alerts. Input a stock ticker or CIK number.

Instructions

Returns a company's profile: identity (name, ticker, CIK, SIC, exchange), market summary (price, returns, 52-week range, volatility), fundamentals summary (revenue, net income, margins, debt ratios), insider trading summary (recent buyer/seller counts and dollar values), and recent insider alerts. Available on all paid EDGAR Alert plans. For a more detailed multi-year fundamentals history use edgaralert_get_company_fundamentals; for a single bundled research-agent payload use edgaralert_get_company_agent_context.

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": {
      "tickerOrCik": "<tickerOrCik>"
    },
    "name": "edgaralert_get_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerOrCikYesStock ticker (e.g. AAPL) or SEC CIK number.
recentAlertsLimitNoNumber of recent insider alerts to include in the profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate safe read-only and idempotent behavior; description adds value by detailing the specific data categories returned and plan availability, with 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?

Description is concise, front-loaded with what the tool returns, and includes necessary context about alternatives without unnecessary words.

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 output schema, the description adequately covers the return content by listing categories and mentions plan availability and alternatives, making it complete for a profile-retrieval tool.

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 descriptions in schema are sufficient. The tool description does not add additional meaning beyond the schema, so baseline score of 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?

The description clearly states the tool returns a company's profile with specific sections (identity, market summary, etc.) and distinguishes itself from siblings by naming alternative tools for more detailed fundamentals or bundled context.

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 mentions it is available on all paid plans and provides clear guidance on when to use alternative tools (edgaralert_get_company_fundamentals for detailed history, edgaralert_get_company_agent_context for bundled payload).

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