FinancialMD

Filing document links

filing_document

Read-onlyIdempotent

Return where a filing's documents are: the primary document on EDGAR, the filing index, the full submission text, the inline XBRL viewer, and a FinancialMD URL that serves the primary HTML document. PDF rendering is not served. Filing-layer read: served with generous limits on every tier. Use it when you need to read or link the text of a filing. 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": {
      "accession": "0000320193-24-000123"
    },
    "name": "filing_document"
  }
}

Input Schema

Name	Required	Description	Default
`accession`	Yes	Accession number, e.g. 0000320193-24-000123.

Output Schema

Name	Required	Description
`data`	No	{ accession, registry, form, filed, primary_doc, document_url, index_url, full_text_url, inline_xbrl_viewer_url, html_url, pdf }
`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.

First observedNov 13, 2026

TDQS

A4.1/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 safety profile is covered. The description adds value beyond that with two real behavioral facts: PDF rendering is not served, and the endpoint is a filing-layer read served with generous limits on every tier, which tells the agent not to worry about rate limiting and not to expect PDFs.

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-loaded with the resource's purpose and the set of returned links, then usage and limits. The link enumeration is a bit dense in one sentence but every sentence carries information; nothing is filler.

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?

With an output schema present, the description needn't detail return values, and it still communicates the link inventory, the PDF limitation, tier/rate behavior, and an escalation path. An agent has enough to call this correctly against its siblings.

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 description coverage is 100% and the single accession parameter is fully documented with a pattern and example in the schema. The description adds no additional meaning about the accession format or behavior, so the baseline 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 ("Return where a filing's documents are") and enumerates the exact link types returned: primary EDGAR document, filing index, full submission text, inline XBRL viewer, and the FinancialMD URL. It also scopes itself as a "Filing-layer read," which separates it from fact/metric siblings like filing_facts.

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?

Gives a clear triggering condition, "Use it when you need to read or link the text of a filing," and names a fallback sibling (request_data) for missing data. It does not explicitly contrast with filing_get or filing_facts, so the agent must infer the boundary from the sibling names alone.

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?