Skip to main content
Glama

Sec Contracts By Company

sec_contracts_by_company
Read-onlyIdempotent

List ONE company's material contracts as filed with the SEC, every Exhibit 10 (credit agreements, employment and severance agreements, leases, license and supply agreements, equity plans), Exhibit 4 (indentures, notes, warrants, registration rights) and Exhibit 2 (merger and acquisition agreements) attached to its 8-K, 10-K, 10-Q, S-1 and S-4 filings, newest first, from SEC EDGAR full-text search. Pass a ticker ("ADBE"), company name ("Adobe") or CIK. Returns exhibit type, the filer's own exhibit description ("EX-10.1 CREDIT AGREEMENT DATED..."), root form, filing date, document URL and accession, grouped by filing. Answers "what credit facility does $TICKER have on file", "show me $COMPANY's executive employment agreements", "which indentures has $TICKER filed since 2023". Read any row with sec_contract_text.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 8,
      "since": "2024-01-01",
      "company": "ADBE",
      "exhibit_type": "EX-4"
    },
    "name": "sec_contracts_by_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNoRoot form filter, e.g. "8-K" or "10-K,10-Q". Omit for all forms.
limitNoMax exhibit documents to return (1-100, default 25), newest filing first.
sinceNoEarliest filing date, YYYY-MM-DD (default: 5 years before today; coverage floor 2001-01-01).
untilNoLatest filing date, YYYY-MM-DD (default: today).
companyYesTicker ("ADBE"), company name ("Adobe Inc") 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: EX-10 material contracts, EX-4 debt/warrant instruments, EX-2 M&A agreements, EX-99 other, any (default) = EX-10 + EX-4 + EX-2, all_exhibits = every EX-* document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world behavior, so the description's added value is in output shape and scoping: source (SEC EDGAR full-text search), ordering (newest first), grouping by filing, and the exact fields returned (exhibit type, filer's own exhibit description, root form, filing date, document URL, accession). With no output schema, that enumeration is genuinely load-bearing. It doesn't mention result caps, pagination, or behavior when a company name resolves to multiple entities.

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?

The core purpose and coverage are front-loaded in the first clause, and every subsequent clause adds usable information (inputs, return fields, example questions, next-step tool). It is dense and slightly run-on, with a long parenthetical enumerating documents, but no sentence is pure 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?

For a six-parameter tool with no output schema, the description supplies the missing return-value picture (fields, grouping, ordering) and hands off full-text retrieval to the sibling. Remaining gaps are edge-case behavior: what happens with ambiguous company names, and whether results beyond the default limit require pagination or just a higher `limit`.

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 3 is the floor, but the description adds real meaning: it explains that `company` accepts three identifier formats and illustrates exhibit families with concrete document types (credit agreements, indentures, warrants, merger agreements) that go beyond the schema's terse 'EX-10 material contracts'. The filing-window default and coverage floor are only in the schema, which is fine given full coverage.

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 (List), a specific resource (one company's material contracts as filed with the SEC) and an explicit scope constraint ('ONE company's'), then enumerates exactly which exhibit families (EX-10, EX-4, EX-2) and filing forms (8-K, 10-K, 10-Q, S-1, S-4) are covered. The per-company scope plus the routing sentence to sec_contract_text makes it distinguishable from the broader sibling search tool.

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 invocation guidance ('Pass a ticker, company name or CIK') and three natural-language example questions that map onto realistic use cases, plus the follow-up move ('Read any row with sec_contract_text'). It stops short of a stated exclusion such as when to prefer sec_contracts_search for multi-company or keyword queries, so the agent must infer that boundary from the 'ONE company' phrasing.

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.