Skip to main content
Glama
Sign In
edgar-mcp

edgar-mcp

by asp53826
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_filings

Full-text search SEC EDGAR filings from 2001 onward, filter by form type and date range, and get direct URLs to matching documents.

Instructions

Full-text search across EDGAR filings from 2001 onward. Returns matching filings with document URLs.

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": {
      "q": "<q>"
    },
    "name": "search_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
formsNo
limitNo
sinceNo
untilNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds valuable context by disclosing the 2001-onward restriction and the return of document URLs, but does not cover pagination, rate limits, or explicit read-only nature, leaving gaps in behavioral disclosure.

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?

The description is concise: two sentences with no filler, directly stating the action and result. It is front-loaded with the core purpose and efficiently conveys essential information.

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

Completeness2/5

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

For a 5-parameter search tool with no output schema, the description is under-specified. It omits parameter semantics, return structure details beyond 'document URLs', and any usage caveats, making it insufficient for an agent to invoke the tool correctly without additional inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no explanation for the 5 parameters (q, forms, limit, since, until). It fails to compensate for the missing schema descriptions, leaving parameter meaning entirely to inference from parameter names.

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 'Full-text search across EDGAR filings' with a specific verb and resource, and distinguishes from siblings like list_filings by emphasizing keyword-based search. It also specifies the date range (2001 onward) and output (document URLs), making the tool's purpose unambiguous.

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 implies the tool is for keyword-based searching of filings, providing clear context. However, it does not explicitly mention alternatives or when not to use this tool, so it lacks the exclusions that would earn a 5.

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