Skip to main content
Glama

fundz

by net.fundz
OverviewDiscussionsAdmin

Search SEC filings

search_sec_filings
Read-onlyIdempotent

Recent SEC 8-K filings with a plain-English AI summary of what actually happened: leadership changes, material agreements, results, restructuring. Use this for "what did company X just file" or to scan a window for material events. Public companies only.

Input Schema

NameRequiredDescriptionDefault
daysNoDays to look back (default 7)
pageNoPage number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more.
limitNoResults per page (default 10, max 50)
company_nameNoCompany name (partial, case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum filings to return (default 10, max 50)"New value: +"Results per page (default 10, max 50)"
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page number, starting at 1 (default 1). Each page holds `limit` results; the reply ends with the total and next_page when there are more.",
+  "type": "number"
+}
  2. First observed

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 openWorld, so the safety profile is covered. The description adds real behavioral content beyond that: 8-K only, AI-summarized rather than raw filings, and a hard scope limit ('public companies only'). It does not describe result volume or ordering.

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?

Two compact sentences with the resource and the differentiator front-loaded, then the usage triggers, then the scope constraint. No redundant restatement of the tool name or schema fields.

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?

No output schema exists, and the description compensates by characterizing the payload (AI summaries of leadership changes, agreements, results, restructuring). Combined with fully-documented parameters and rich annotations, an agent has everything needed to call and interpret it.

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%, with defaults, max limit, and pagination behavior all documented in the schema itself. The description adds only an implicit hint that a time window and company can be filtered, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Recent SEC 8-K filings') with a differentiating detail — the plain-English AI summary of material events — which distinguishes it from a raw-text sibling like search_filing_text. It does not name any sibling explicitly, so an agent must infer the boundary itself.

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 concrete when-to-use triggers: 'what did company X just file' and scanning a window for material events. There is no stated when-not or explicit alternative routing, but the usage context is unambiguous.

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

All fundz toolsInspect
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