automaton

company_facts__dossier

Company, sanctions and domain facts in one call: SEC EDGAR identity/filings and full-text filing search, OFAC SDN + EU sanctions screening, RDAP domain facts, DNS. $0.01 per call in USDC on Base. Free previews available. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/company-facts/dossier

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "company_facts__dossier"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	SEC EDGAR full-text query; quote phrases, e.g. "going concern"
`enddt`	No	End date YYYY-MM-DD
`forms`	No	Comma-separated form types, e.g. 10-K,8-K
`limit`	No	Max results (default 10, max 40)
`startdt`	No	Start date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 12, 2026

addedInput schema / properties / enddt

Added value: +{
+  "description": "End date YYYY-MM-DD",
+  "type": "string"
+}

addedInput schema / properties / forms

Added value: +{
+  "description": "Comma-separated form types, e.g. 10-K,8-K",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Max results (default 10, max 40)",
+  "type": "integer"
+}

removedInput schema / properties / name

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

addedInput schema / properties / q

Added value: +{
+  "description": "SEC EDGAR full-text query; quote phrases, e.g. \"going concern\"",
+  "type": "string"
+}

addedInput schema / properties / startdt

Added value: +{
+  "description": "Start date YYYY-MM-DD",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "q"
+]
```

Changed3 schema fields changedNov 7, 2026
- removedInput schema / properties / company
```
Removed value: -{
-  "type": "string"
-}
```
- removedInput schema / properties / domain
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / name
```
Added value: +{
+  "type": "string"
+}
```
AddedNov 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the payment model ($0.01 per call in USDC on Base, eip155:8453, via x402 in params._meta["x402/payment"]), the HTTP verb and URL, and the existence of free previews — meaningful context. It does not disclose failure semantics across the four upstream sources (does one failing source fail the whole call?), rate limits, or what the response contains, which matters more here given there is no output schema.

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?

The capability list is front-loaded and efficient, but the pricing is stated twice in near-identical form ("$0.01 per call in USDC on Base" followed by "Price: $0.01 per call in USDC on Base (eip155:8453)"), and "Free previews available" is stranded between the two. One sentence of the description is pure duplication and could be removed without loss.

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 five-parameter aggregation tool with no output schema and no annotations, the description covers the data sources queried, cost and payment mechanics, and invocation transport, which is most of what an agent needs to decide and pay. The remaining gap is what actually comes back and how partial failures behave, which is a real but secondary omission given the source list serves as a rough proxy for the payload.

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 q, startdt, enddt, forms and limit are already documented with examples and defaults in the schema. The description adds no parameter-level meaning of its own — it does not say, for instance, that the date/form filters apply only to the EDGAR full-text portion and not to the sanctions or domain data.

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

Purpose4/5

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

The description names a concrete verb-and-resource combination: an aggregated "Company, sanctions and domain facts in one call" spanning SEC EDGAR identity/filings, full-text search, OFAC SDN + EU screening, RDAP and DNS. The phrase "in one call" implicitly separates it from the narrower siblings (company_facts__filings, __fulltext, __domain, __risk), though it never names them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the bundled alternative to calling the individual source tools separately, and "Free previews available" hints at a try-before-paying path. There is no explicit when-to-use/when-not statement, no guidance on choosing this over company_facts__snapshot or the per-source tools, and no note about latency or cost trade-offs.

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

All automaton 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?