Skip to main content
Glama

Signal Nodus SEC Filings

by ai.signalnodus

Recent SEC filings

recent_filings
Read-only

List a company's most recent SEC filings with form type, dates, accession number, and a direct document URL. Optionally filter to one form type (10-K, 10-Q, 8-K, 4, S-1...). Covers EDGAR's recent-filings index, which holds roughly the last 1000 filings; older history is not searched, and the response says so when it exists. This is the canonical filing record, not commentary about it. Costs $0.01 per call. No subscription: present a credit key or a machine payment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formNoOptional exact form type filter, e.g. 10-K, 10-Q, 8-K, 4.
limitNoHow many filings to return (1-50, default 10).
companyYesTicker symbol (e.g. AAPL) or SEC CIK number (e.g. 320193).

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description complements these by disclosing the index depth, the fact that the response notes when older history exists, and the $0.01 cost with no subscription but requiring a credit key or machine payment. This is rich behavioral context beyond what annotations offer.

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?

Every sentence adds value: first states purpose and output, second mentions optional filter, third explains scope and limitation, fourth clarifies it's canonical data, fifth covers cost and access. No filler, front-loaded with the core function.

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 tool with 3 params and no output schema, the description sufficiently conveys what to expect (fields returned), the boundary (last ~1000 filings), and the commercial access model. It is complete for an agent to invoke correctly without needing additional context.

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 already documents all three parameters with full descriptions (100% coverage). The description adds marginal value by reiterating the form-type filter and ticker/CIK options, but does not exceed what the schema provides, so baseline 3 is appropriate.

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 lists a company's most recent SEC filings and names the returned fields (form type, dates, accession number, URL). It distinguishes from siblings by defining the scope (EDGAR's recent-filings index, ~1000 filings) and positioning this as the canonical record, not commentary.

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?

It gives clear context on when to use: for recent filings within the ~1000 limit, and for canonical records rather than commentary. It notes the limitation that older history is not searched, implying that other tools (e.g., edgar_search) may cover broader history, though it doesn't name them explicitly.

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

All Signal Nodus SEC Filings 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

A3.5/5.0
Disambiguation3/5

Most tools have clearly written descriptions, but several pairs overlap semantically: token_price/token_report, latest_filings/recent_filings, and institutional_holdings/who_holds/activist_stakes all require careful reading to pick the right one. The overlap is not severe enough for a 2, but it is still more than the occasional confusion.

Naming Consistency3/5

Names are consistently snake_case and mostly descriptive, but the set does not follow one naming convention. It mixes noun phrases (crop_data, token_report, insider_trades) with verb phrases (lookup_company, compare_filings, verify_financial_claim), and pairs like latest_filings/recent_filings create avoidable confusion.

Tool Count2/5

31 tools is too many for what is nominally an SEC Filings server, and the scope sprawls into unrelated domains such as EVM gas, tokens, prediction markets, crop data, and x402 auditing. The count does not feel earned by a coherent workflow; it feels like an uncurated bundle of endpoints.

Completeness3/5

The SEC filing workflow is reasonably covered: company lookup, search, latest/recent filings, section extraction, 8-K events, comparisons, ownership filings, and XBRL financial checks are all present. However, there is no full-filing retrieval endpoint, no deep company financial history beyond a single concept, and many non-SEC subdomains are only one-off data points, so the overall surface is still incomplete.

Resources