Skip to main content
Glama

Sec Contracts Search

sec_contracts_search
Read-onlyIdempotent

Find SEC material-contract exhibits by CLAUSE LANGUAGE — credit agreements, merger agreements, indentures, employment and severance agreements, change-of-control agreements, license and supply agreements, warrants — searching the full text of every Exhibit 10 / Exhibit 4 / Exhibit 2 attached to 8-K, 10-K, 10-Q, S-1 and S-4 filings in SEC EDGAR full-text search (2001 to today). The inverted question: "credit agreements filed since 2025 with a change of control clause", "employment agreements with a 2x severance multiple", "indentures with a make-whole redemption", "merger agreements with a reverse termination fee". Returns one row per exhibit document: company, CIK, ticker, root form, filing date, exhibit type (EX-10.1, EX-4.2...), the filer's exhibit description ("EX-10.1 CREDIT AGREEMENT"), a text snippet around the matched phrase, the exhibit document URL, accession number and the filing index page — plus the same hits grouped by filing with each filing's exhibit list. Narrow by exhibit family (EX-10 material contracts, EX-4 debt instruments/indentures/warrants, EX-2 merger and acquisition agreements), root form, filing-date window, one company (name, ticker or CIK) or SIC industry code (7372 software, 2834 pharma, 6022 banks). Feed document_url (or adsh + filename + cik) to sec_contract_text to read the agreement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sicNoRestrict to an SIC industry code, e.g. "7372" (prepackaged software), "2834" (pharmaceutical preparations), "6022" (state commercial banks), "1311" (crude petroleum and natural gas). Comma-separate several.
formNoRoot form the exhibit was attached to, e.g. "8-K", "10-K", "10-Q", "S-1", "S-4", "DEF 14A". Comma-separate several: "8-K,10-K". Omit for all forms.
limitNoMax exhibit documents to return (1-50, default 10). Each returned exhibit costs one bounded document read for its snippet when include_snippets is on.
matchNophrase (default): the words must appear together in order. all: every word must appear somewhere in the document. any: at least one word. Use `all` for concept searches like "severance multiple change control".
queryYesThe clause or phrase to find in exhibit text, e.g. "change of control", "make-whole", "reverse termination fee", "most favored nation". Multi-word input is matched as an exact phrase by default (see `match`). Double quotes inside the value are passed through, so "\"change of control\" severance" searches the phrase AND the word.
sinceNoEarliest filing date, YYYY-MM-DD. Full-text coverage starts 2001-01-01; earlier values are clamped. Default: 2 years before today.
untilNoLatest filing date, YYYY-MM-DD. Default: today.
companyNoRestrict to one filer: ticker ("ADBE"), company name ("Adobe") or CIK ("796343"). Names are resolved against the SEC ticker list first; unlisted names fall back to EDGAR's entity-name filter.
exhibit_typeNoExhibit family to keep. EX-10 = material contracts (credit, employment, license, supply, leases). EX-4 = instruments defining security-holder rights (indentures, notes, warrants, registration rights). EX-2 = plans of acquisition, reorganization, merger. EX-99 = additional exhibits (press releases, investor decks). any (default) = EX-10 + EX-4 + EX-2, the material-contract set. all_exhibits = every EX-* document. "10", "ex10" and "EX-10.1" are all read as EX-10.
include_snippetsNoFetch each matched exhibit and return a ~440-character window around the first occurrence of the phrase. Default true. Set false for a faster list-only answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds cost semantics ('Each returned exhibit costs one bounded document read'), default date windows, clamping behavior for pre-2001 dates, and the include_snippets performance tradeoff.

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?

Purpose is front-loaded and the dense single paragraph flows logically from what it finds to output fields to narrowing and follow-up. It is somewhat long and lists many agreement types and examples that are illustrative rather than strictly necessary.

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?

With no output schema, the description carries the return-value burden and does so: one row per exhibit document with named fields, grouped hits by filing, and a pointer to sec_contract_text for reading the agreement. Defaults and cost are also covered, making it complete for a complex search tool.

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%, so the schema already documents all ten parameters in detail. The description adds conceptual framing through example queries and the inverted-search framing, but little parameter-specific meaning beyond what the schema already provides.

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?

States a specific verb and resource: find SEC material-contract exhibits by clause language. The scope is sharply differentiated from sibling tools via 'by CLAUSE LANGUAGE' and the follow-up pointer to sec_contract_text, so an agent can route without opening another schema.

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?

Provides clear context with concrete example queries and explains narrowing by exhibit family, form, date, company, and SIC. It does not explicitly name sec_contracts_by_company as the alternative or state when not to use this tool, so it falls short of full alternative routing.

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.