ffd-mcp

search_fee_filings

Search SEC filings for Exhibit 107 fee tables. Input ticker, name, or CIK to get accession numbers, form types, and EDGAR links for fee parsing.

Instructions

Find a company's recent registration statement filings that contain Exhibit 107 fee disclosures. Returns accession numbers, form types, filing dates, and EDGAR URLs. Use the results to call get_fee_exhibit for full fee table parsing. Resolves tickers, company names, or CIK numbers automatically.

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": {
      "company": "<company>"
    },
    "name": "search_fee_filings"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max filings to return (default 10)
`company`	Yes	Ticker symbol, company name, or CIK number
`form_types`	No	Filter to specific form types (e.g. ['S-1', 'S-3']). Defaults to all registration forms.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It discloses return fields and the input resolution behavior, which is solid. It omits potential limitations (e.g., what 'recent' means, error handling) but is sufficiently informative for a read-only search tool.

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 tightly written sentences: purpose, return fields, and workflow. No redundant fluff, front-loaded with the most important 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 simple search tool with 3 params and no output schema, it covers the essential aspects: what it finds, what it returns, and how to proceed. It does not detail ordering/pagination but the limit param in schema addresses one form of control.

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%, with each parameter already described. The description adds minimal param-specific semantics beyond emphasizing automatic identifier resolution, which is also in the schema. Thus the 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?

The description clearly states the tool finds registration statement filings with Exhibit 107 fee disclosures, and specifies the returned fields (accession numbers, form types, filing dates, EDGAR URLs). It differentiates from siblings by directing users to call get_fee_exhibit for full parsing, establishing a clear niche.

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?

It provides a concrete workflow by instructing to use results with get_fee_exhibit, and states input resolution (tickers, names, CIKs). It does not explicitly list exclusions or alternatives like search_filings_by_fee, but the tool's role is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server