Skip to main content
Glama

Research data (x402)

filings_search

$0.005 via x402: Full-text search across EDGAR filings (since 2001): q (phrase or words), optional form and since (YYYY-MM-DD); returns up to 25 hits with company, CIK, form, filed date, file description and document URL. Pay 0.005 USDC through https://store.agentexchange.work/gw/filings/search?q=%22artificial+intelligence%22&form=8-K&since=2026-10-01 Via the Agent Exchange store gateway; settled by Coinbase.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "filings_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesq
formNoform
sinceNosince
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the $0.005 x402 cost, the USDC payment flow via the store gateway, and that requesting without the x_payment payload returns the price. It also states the return cap (up to 25 hits) and the fields returned. It stops short of describing pagination or rate limits.

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?

Information-dense and mostly front-loaded, but it leads with cost ('$0.005 via x402') rather than purpose and crams params, returns, and payment into one long run-on sentence with an inline example URL. Every element earns its place, though structure could be cleaner.

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?

With no output schema, the description correctly explains the return shape (up to 25 hits with company, CIK, form, filed date, file description, document URL) and covers the payment requirement, which is essential for correct invocation. The main gap is pagination behavior for results beyond the 25-hit cap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the bare schema labels: q accepts a phrase or words, form filters by form type, and since uses YYYY-MM-DD format with an embedded example URL. It adds meaning over the schema's one-word parameter names.

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?

The description states a specific verb and resource ('Full-text search across EDGAR filings') plus scope (since 2001) and the searchable fields, so an agent knows exactly what it does. It doesn't explicitly name the sibling tools it differs from (filings_company, filings_facts, filings_filings), but the 'full-text search' verb strongly implies the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the sibling filings tools, no prerequisites beyond payment, and no exclusions. The only usage signal is the implied 'full-text search' framing, which is not enough to route confidently among four filings siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources