FinancialMD

One filing

filing_get

Read-onlyIdempotent

Return one filing by its SEC accession number: registry, form, period end, fiscal year and period, filing date and acceptance time, the primary document name and its SEC source URL, and the accession it amends (for 10-K/A and 10-Q/A). The document itself is not returned (it can be megabytes); read it from source_url, and read its numbers with financials_as_reported. Filing-layer read: served with generous limits on every tier. Use it when you hold an accession number and need the filing's form, dates and source URL. 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_get"
  }
}

Input Schema

Name	Required	Description	Default
`accession`	Yes	SEC accession number in dashed form, for example 0000320193-24-000123.

Output Schema

Name	Required	Description
`data`	No	The filing: accession, registry, form, period_end, fiscal_year, fiscal_period, filed, accepted_at, primary_doc, source_url, amends, pipeline_version.
`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.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low. The description nevertheless adds real behavior: the document body is explicitly NOT returned and why (megabytes), and that the call is "served with generous limits on every tier," which tells the agent it can call this freely. It omits error behavior when an accession is unknown, which keeps it from a 5.

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 return payload, followed by the boundary (document not included), the access profile, and the routing rule — a sensible order. The initial field enumeration is dense and reads slightly like a schema restatement, but each sentence still earns its place by preventing a wrong downstream call.

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 single-parameter lookup with a rich annotation set and an output schema, the definition covers the payload boundary, the follow-up paths (source_url, financials_as_reported), and a fallback (request_data). Nothing an agent needs in order to select and invoke 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% and the schema already documents the dashed pattern with an example, so the description carries no extra burden. The prose adds only a light gloss ("by its SEC accession number") and a note that 10-K/A and 10-Q/A filings carry an amends pointer, which is output semantics rather than parameter meaning. Baseline 3 is correct.

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 one filing by its SEC accession number") and enumerates exactly which attributes come back (registry, form, period end, fiscal year/period, dates, acceptance time, primary document, source URL, amended accession). It is clearly differentiated from filing_document (document bytes) and financials_as_reported (numbers) by naming both siblings inline.

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?

Explicit routing: "Use it when you hold an accession number and need the filing's form, dates and source URL." It also names the alternatives for the adjacent needs — read the document from source_url, read numbers with financials_as_reported, and call request_data if something is missing. This is as close to a when/when-not/alternatives statement as a one-param lookup tool needs.

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?