FedWatch — Federal Funding & Lien Watcher

securities_search

Search SEC EDGAR filings. Source sec_edgar_filings (default): full-text search across filing text (keyword required) with optional form filter (e.g. 'D', '8-K', '13F-HR'), or a per-CIK submissions view when cik is given (recent-filings window — 13F coverage is that window only, labelled as such). EDGAR's own hit total is carried; when EDGAR reports it as a lower bound (relation gte) the response says so. Watch a CIK or a keyword+form query for new-filings alerts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "securities_search"
  }
}

Input Schema

Name	Required	Description
`cik`	No	CIK number — switches to the per-filer submissions view
`form`	No	Form filter, comma-separated, e.g. 'D' or '8-K,13F-HR'
`limit`	No	Maximum returned records (tier-capped)
`keyword`	No	Full-text keyword/phrase searched across filing text
`source_id`	No	Source id: sec_edgar_filings (default)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.3/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 substantial work: it discloses the default source, the keyword requirement, that 13F coverage in the CIK view is limited to the recent-filings window, and that EDGAR's hit total is carried and flagged as a lower bound (relation gte). It never states read-only/safety posture or pagination behavior, which a search tool of this kind should still mention.

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?

Front-loaded with the one-line purpose, then mode detail, then caveats — a sensible ordering. The prose is dense with em-dash asides and packs several ideas into long sentences, but nearly every clause carries operational information rather than filler.

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?

No annotations and no output schema, so the description must cover behavior and return semantics; it does so partially by explaining the hit-total lower-bound signalling and the coverage caveat on 13F filings. What a result record actually contains is left unstated, which is the remaining gap for a 5-parameter search tool.

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 genuine semantics the schema does not: keyword is mandatory for the full-text path, cik changes the entire view rather than merely filtering, and form accepts comma-separated lists. The interaction between cik and keyword is the key calling decision and is only explained here.

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?

Opens with a specific verb+resource ('Search SEC EDGAR filings') and immediately enumerates the two operating modes — full-text keyword search and per-CIK submissions. The securities/filings domain alone separates it from every sibling (courts_search, contracts_search_awards, etc.).

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?

States the mode-selection rule clearly: keyword drives full-text search ('keyword required'), supplying cik switches to the per-filer submissions view, and form can be combined with either. It also names the watch/alerts use case. It stops short of naming a sibling alternative or an explicit when-not-to-use this tool.

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

All FedWatch — Federal Funding & Lien Watcher tools Inspect

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

Need Help?