Skip to main content
Glama
yyordanov-tradu

stock-scanner-mcp

edgar_company_filings

Read-only

Retrieve the most recent SEC filings for any public company, including 10-K annual reports, 10-Q quarterly reports, and 8-K current events.

Instructions

Retrieve the most recent official filings for a specific company. Use this to find a company's latest 10-K (annual), 10-Q (quarterly), or 8-K (current events) reports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g. 'AAPL')
formsNoForm types (e.g. ['10-K', '10-Q']). Default: all.
limitNoMax results (default: 10, max: 50)
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's addition of 'most recent official filings' provides some context but does not significantly enhance transparency beyond what annotations already provide.

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 clear, efficient sentences. First sentence defines purpose, second gives examples. No extraneous information.

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

Completeness4/5

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

For a tool with 3 parameters, high schema coverage, and no output schema, the description adequately explains the tool's function and typical use cases, though it could mention default limit behavior (covered by 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?

With 100% schema description coverage, the baseline is 3. The description adds context about typical form types (10-K, 10-Q, 8-K) but does not add new meaning beyond what the schema already provides for parameters.

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 verb 'Retrieve' and specific resource 'official filings' for a specific company, and distinguishes from siblings like edgar_company_facts or edgar_insider_trades by focusing on filings.

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?

The description tells when to use the tool ('to find a company's latest 10-K, 10-Q, or 8-K reports'), but does not explicitly mention when not to use or provide alternatives among siblings.

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/yyordanov-tradu/stock-scanner-mcp'

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