Skip to main content
Glama

FilingFirehose

by com.filingfirehose

search_atm_offerings

Search recent SEC at-the-market (ATM) equity offerings from the past 72 hours.

Pulls from S-3 / 424B5 family filings where our parser flagged ATM-offering
indicators in the body language.

Args:
    sales_agent: Filter by sales agent name (substring, case-insensitive).
        Examples: 'Cantor Fitzgerald', 'Jefferies', 'Roth Capital',
        'H.C. Wainwright'.
    min_shelf_million_usd: Minimum shelf size in millions USD.
    limit: Max results (1-50, default 25).

Returns:
    JSON list with shelf_size_usd, is_atm, sales_agents, use_of_proceeds_excerpt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
sales_agentNo
min_shelf_million_usdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.2/5.0
Behavior3/5

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

The description discloses the data source (SEC filings with parser flags) and temporal scope (72 hours), but does not cover potential latency, rate limits, or data freshness guarantees. With no annotations, it provides adequate but not exhaustive transparency.

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?

The description is structured with purpose, source, args, and returns sections. It is information-dense but not verbose, though some parameter repetition could be streamlined.

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?

Given the presence of an output schema and low complexity (3 optional params), the description covers usage adequately. It could add more on filtering behavior or edge cases, but remains complete enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description fully compensates by detailing each parameter with types, defaults, examples, and constraints (e.g., substring, case-insensitive for sales_agent, 1-50 for limit).

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 searches recent SEC at-the-market equity offerings from the past 72 hours, using a specific verb-resource combination that distinguishes it from siblings like search_13d_filings or search_8k_filings.

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?

The description explains when to use the tool (searching recent ATM offerings from S-3/424B5 filings) and provides parameter examples, but lacks explicit guidance on when not to use it or alternatives beyond sibling tool names.

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