Skip to main content
Glama

FilingFirehose

by com.filingfirehose

get_filing

Fetch one filing by SEC accession number, regardless of recency.

Useful when an agent has an accession number from a citation or earlier
tool call and needs the parsed details.

Args:
    accession_number: SEC accession in 'XXXXXXXXXX-YY-NNNNNN' format.

Returns:
    JSON for the filing if found in our archive, or {"found": false}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accession_numberYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description bears the burden. It notes 'regardless of recency' and implies a safe read operation. Does not explicitly state read-only or idempotent, but conveys core behavior.

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?

Extremely concise: one sentence plus structured Args/Returns. Every sentence is informative without redundancy.

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?

The tool has one parameter and a straightforward return. The description covers when to use, parameter format, and return structure. Could mention error handling, but adequate for this simplicity.

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 0%, but the description provides the required format for accession_number ('XXXXXXXXXX-YY-NNNNNN'). This adds meaning beyond the JSON schema, though more detail could help.

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 specifies a concrete verb ('Fetch one filing') and resource ('by SEC accession number'), and distinguishes itself from sibling search tools which search by other criteria.

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?

Explicitly states when to use: 'when an agent has an accession number...needs the parsed details'. Does not explicitly list when not to use, but the context is clear enough.

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

All FilingFirehose toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a distinct purpose: get_filing retrieves a specific filing by accession number, while the three search tools focus on different filing types (13D/13G, 8-K, ATM offerings). No overlap or ambiguity between them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: get_filing and search_<type>_filings. The slight difference between 'get' and 'search' is appropriate for the distinct operations (retrieval vs. search).

Tool Count5/5

With 4 tools, the server is well-scoped. It covers both retrieval of a specific filing and search across three important SEC filing categories. The count feels neither too thin nor too heavy for the domain.

Completeness3/5

The tools cover a niche but useful subset of SEC filings. However, there is no general search (e.g., by company name or date range) and no support for other common filings like 10-K or 10-Q. The 72-hour recency limit also restricts coverage. Gaps exist for broader SEC research.

Resources