Skip to main content
Glama

Sec Contract Text

sec_contract_text
Read-onlyIdempotent

Read the text of ONE SEC exhibit document, a credit agreement, merger agreement, indenture, employment agreement or any other EX-10 / EX-4 / EX-2 attachment, as clean plaintext, paged. Pass the document_url from sec_contracts_search or sec_contracts_by_company (or adsh + filename + the registrant's cik). Returns up to max_chars (default 50,000) from offset with truncated + next_offset for the next window; a very large exhibit (a syndicated credit agreement can run 2-4 MB of HTML) is read up to 4 MB and flagged raw_truncated. Use to quote the actual clause, the definition of "Change of Control", the severance multiple, the termination-fee amount, the interest-rate grid, the covenants, after sec_contracts_search located the agreement.

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": {
      "url": "https://www.sec.gov/Archives/edgar/data/712537/000071253725000088/fcf-ex103_20250331xchangeo.htm",
      "max_chars": 1500
    },
    "name": "sec_contract_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoThe REGISTRANT's CIK (returned as `cik` on every search row). Needed with adsh + filename because the Archives path is keyed by the registrant, and the filing-agent CIK that prefixes many accession numbers does not resolve. Omit only when the accession prefix is the registrant itself.
urlNoThe exhibit's document URL on www.sec.gov/Archives, exactly as returned in `document_url` by sec_contracts_search. Preferred over adsh + filename.
adshNoAccession number, dashed or not (e.g. "0000712537-25-000088"). Use with `filename` and `cik`.
findNoOptional phrase to jump to: the page starts ~300 characters before its first occurrence instead of at `offset`. Use to land directly on the "Change of Control" definition or the "Termination Fee" section.
offsetNoCharacter offset to start from (default 0). Pass the prior result's next_offset to page forward.
filenameNoThe exhibit file name inside the filing, e.g. "fcf-ex103_20250331xchangeo.htm" (the part after the colon in a search hit's `_id`, also returned as `filename`).
max_charsNoMax characters in this page (1000-100000, default 50000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds substantial behavior beyond that: default page size, offset/truncated/next_offset paging contract, the 4 MB exhibit ceiling with a `raw_truncated` flag, and the warning that syndicated credit agreements can be 2-4 MB of HTML. That is exactly the operational context an agent needs to avoid misreading a partial result.

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?

A single dense paragraph with the core purpose front-loaded and no filler sentences; nearly every clause carries paging, sizing, or routing information. It loses a point for re-stating defaults (50,000 chars, offset 0) that the schema already documents, and for being a wall of text where a short bulleted paging contract would scan faster.

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?

There is no output schema, and the description compensates by describing the return shape in prose: clean plaintext, `truncated` and `next_offset` for continuation, and `raw_truncated` for oversized exhibits. Combined with the 4 MB cap and the two input paths, an agent knows both how to call it and how to interpret what comes back.

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?

With 100% schema coverage the baseline is 3, and the description earns above that by explaining precedence ('url' preferred over adsh + filename + cik), why registrant cik is required (the filing-agent prefix does not resolve), and how `find` shifts the window ~300 characters before the match. It adds somewhat less on `offset` and `max_chars`, whose defaults are restated rather than extended.

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?

The description opens with a specific verb and resource ('Read the text of ONE SEC exhibit document') and enumerates the exact document classes (credit agreement, merger agreement, indenture, employment agreement, EX-10/EX-4/EX-2 attachments). It also names the two sibling tools that feed it, so an agent can distinguish it from sec_contracts_search and sec_contracts_by_company without opening a schema.

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

Usage Guidelines5/5

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

It states the sequencing explicitly: use after sec_contracts_search has located the agreement, and pass the `document_url` returned by search or by_company. It also gives a concrete in-document navigation pattern (use `find` to land on the 'Change of Control' definition or 'Termination Fee' section) rather than leaving clause retrieval to inference.

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.