FinancialMD

Search filing text

filing_search

Read-onlyIdempotent

Keyword search across the text of EDGAR documents filed since 2001 (10-K, 10-Q, 8-K and their exhibits, proxies, S-1s...) through SEC EDGAR full-text search. Put a phrase in double quotes. Returns documents, best match first, each with its form, filing date, the companies on it (FinancialMD ids where covered) and links to the document and the filing index. Use it to find which companies mention a risk, customer, product or term; then read numbers with financials_standardized or the document with filing_document. Filing-layer read: served with generous limits on every tier. If a dataset, field, company or analysis you need is missing, call request_data.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "\"going concern\"",
      "from": "2026-01-01",
      "forms": "10-K"
    },
    "name": "filing_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Words to find; a phrase in double quotes matches exactly. Letters, digits, spaces and common punctuation.
`to`	No	Filed on or before (YYYY-MM-DD).
`from`	No	Filed on or after (YYYY-MM-DD).
`page`	No	Page number, 1-based.
`forms`	No	Comma-separated form types, for example "10-K,10-Q".
`limit`	No	Maximum number of periods or items to return (default 10, at most 100).
`company`	No	Optional: only this company's documents. Company identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.

Output Schema

Name	Required	Description
`data`	No	{ total, items: [{ accession, form, file_type, filed, period_ending, companies: [{ cik, name, fmd_id, ticker }], document_url, index_url }], next_page, source }
`meta`	No	Request metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
`error`	No	Present only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

changedInput schema / properties / company / description

Previous value: -"Optional: only this company's documents. Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Optional: only this company's documents. Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description focuses on what they cannot convey: coverage since 2001, result ordering (best match first), and the fields returned per hit including covered FinancialMD ids and document/index links. The 'generous limits on every tier' note adds useful rate-limit context. Pagination behavior is only implied via the schema's page/limit parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core scope, then the quoting rule, then the return shape, then the routing advice. The prose is dense but every sentence earns its place; the parenthetical form list is slightly long but genuinely informative.

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?

For a seven-parameter search tool with an output schema, the definition covers scope, query syntax, result ordering, returned fields and handoffs to sibling tools. Nothing an agent needs in order to call it correctly is missing.

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%, so every parameter is already documented, including phrase quoting in double quotes and the company identifier formats. The description reinforces the phrase-quoting convention but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource: keyword search across the text of EDGAR documents since 2001, with the form types covered. It is clearly distinguishable from filing_document (full document read) and financials_standardized (numbers), which it names directly.

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?

Gives explicit when-to-use guidance: find which companies mention a risk, customer, product or term, then route to financials_standardized for numbers or filing_document for the document. It also names the escape hatch, request_data, for missing datasets or fields.

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

All FinancialMD tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?