Synthex Forge — x402 Paid Agent Services

Extract Sec Filing

extract_sec_filing

Read-onlyIdempotent

Sec Extract. use it rather than extract_contract_terms for sec filing, not contract terms; an object with 20 fields including Accept-Encoding, User-Agent. $0.05 USDC.

Input Schema

Name	Required	Description	Default
`ticker`	No	The ticker this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`cik`	No	The `cik` field of the response.
`sic`	No	The `sic` field of the response.
`form`	No	The `form` field of the response.
`note`	No	A note on how the answer was produced.
`detail`	Yes	Human-readable explanation of the verdict.
`ticker`	No	The `ticker` field of the response.
`cik_int`	No	The `cik_int` field of the response.
`website`	No	The `website` field of the response.
`sourceUrl`	No	The `sourceUrl` field of the response.
`User-Agent`	No	The `User-Agent` field of the response.
`dataSource`	No	The `dataSource` field of the response.
`filingDate`	No	The `filingDate` field of the response.
`reportDate`	No	The `reportDate` field of the response.
`companyName`	No	The `companyName` field of the response.
`fetchedAtUtc`	No	The `fetchedAtUtc` field of the response.
`fiscalYearEnd`	No	The `fiscalYearEnd` field of the response.
`sicDescription`	No	The `sicDescription` field of the response.
`Accept-Encoding`	No	The `Accept-Encoding` field of the response.
`latestPeriodicFiling`	No	The `latestPeriodicFiling` field of the response.
`stateOfIncorporation`	No	The `stateOfIncorporation` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 31, 2026

addedOutput schema / properties / Accept-Encoding

Added value: +{
+  "description": "The `Accept-Encoding` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / User-Agent

Added value: +{
+  "description": "The `User-Agent` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / cik

Added value: +{
+  "description": "The `cik` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / cik_int

Added value: +{
+  "description": "The `cik_int` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / companyName

Added value: +{
+  "description": "The `companyName` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / dataSource

Added value: +{
+  "description": "The `dataSource` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / fetchedAtUtc

Added value: +{
+  "description": "The `fetchedAtUtc` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / filingDate

Added value: +{
+  "description": "The `filingDate` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / fiscalYearEnd

Added value: +{
+  "description": "The `fiscalYearEnd` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / form

Added value: +{
+  "description": "The `form` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / latestPeriodicFiling

Added value: +{
+  "description": "The `latestPeriodicFiling` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / reportDate

Added value: +{
+  "description": "The `reportDate` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sic

Added value: +{
+  "description": "The `sic` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sicDescription

Added value: +{
+  "description": "The `sicDescription` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sourceUrl

Added value: +{
+  "description": "The `sourceUrl` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / stateOfIncorporation

Added value: +{
+  "description": "The `stateOfIncorporation` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / ticker

Added value: +{
+  "description": "The `ticker` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / website

Added value: +{
+  "description": "The `website` field of the response.",
+  "type": "object"
+}

addedOutput schema / required
```
Added value: +[
+  "detail"
+]
```

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context — a $0.05 USDC cost — but the remainder ("an object with 20 fields including Accept-Encoding, User-Agent") is opaque and looks like raw header metadata rather than meaningful behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the fragments are not front-loaded coherently — cost, routing, and return shape are jammed into one semicolon chain, and the "Accept-Encoding, User-Agent" clause adds noise rather than signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return documentation isn't strictly required, yet the description muddies it with a confusing field sample. For a paid extraction tool the agent still lacks the essentials: what filing content is returned, and whether payment authorization must be arranged beforehand.

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?

There is a single `ticker` parameter with 100% schema description coverage, so the schema carries the burden and baseline 3 applies. The description says nothing about the ticker's format, case sensitivity, or what happens when it's omitted (it's optional with an empty default).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Sec Extract" largely restates the title, but the phrase "for sec filing, not contract terms" does identify the resource and separate it from extract_contract_terms. An agent can infer it extracts data from SEC filings, though the description never states the action or what is extracted explicitly.

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?

It explicitly routes the agent: use this rather than `extract_contract_terms` for SEC filings, not contract terms. This is a clear selection rule against the closest sibling, though no further conditions (e.g., filing types, when extraction is needed) are given.

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

All Synthex Forge — x402 Paid Agent Services 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.