automaton

company_facts__filings

Recent SEC EDGAR filings for a company name. 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/filings

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "company_facts__filings"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed4 schema fields changedNov 6, 2026

addedInput schema / properties / company
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / forms

Removed value: -{
-  "description": "CSV of form types, e.g. 8-K,10-K",
-  "type": "string"
-}

removedInput schema / properties / q

Removed value: -{
-  "description": "Phrase to search",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "q"
-]
```

Changed3 schema fields changedNov 6, 2026
- addedInput schema / properties / forms / description
```
Added value: +"CSV of form types, e.g. 8-K,10-K"
```
- addedInput schema / properties / q / description
```
Added value: +"Phrase to search"
```
- addedInput schema / required
```
Added value: +[
+  "q"
+]
```

Changed6 schema fields changedNov 3, 2026

removedInput schema / description
```
Removed value: -"q required."
```

removedInput schema / properties / date

Removed value: -{
-  "description": "start:end date range",
-  "type": "string"
-}

removedInput schema / properties / forms / description
```
Removed value: -"CSV form types"
```

removedInput schema / properties / limit

Removed value: -{
-  "description": "1-50, default 20",
-  "type": "integer"
-}

removedInput schema / properties / q / description
```
Removed value: -"Search phrase"
```
removedInput schema / required
```
Removed value: -[
-  "q"
-]
```

AddedNov 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations supplied, the description does add real behavioral context absent from structured fields: a per-call price ($0.01 USDC on Base), the x402 payment payload location (params._meta['x402/payment']), and the underlying HTTP endpoint. However it never defines what 'recent' means (count or date window), nor failure/payment-rejection behavior, which are meaningful gaps for an unpaid-call scenario.

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 in the first clause, followed by the commercial and transport facts in a compact run-on. No filler; the raw HTTP URL is marginally redundant for an MCP caller but is short and useful for debugging.

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?

For a one-parameter, output-schema-less lookup the description covers purpose, cost, payment mechanics, and endpoint. It still omits response shape and the meaning of 'recent', leaving the agent to discover them by paying for a call.

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 coverage is 0% and the single 'name' parameter is undocumented, so the description carries the burden. It does establish that the value is a company name, but leaves unresolved whether a ticker or CIK is accepted and what happens since the parameter is not marked required.

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?

Names a specific resource and scope: 'Recent SEC EDGAR filings for a company name' tells the agent exactly what comes back. It does not differentiate from siblings that overlap heavily (company_facts__lookup, company_facts__dossier, edgar__company, edgar__financials), so selection still requires guesswork.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all. An agent cannot tell from the description whether to call this instead of company_facts__dossier or edgar__company when it needs filings, and no prerequisites or alternative routing are given.

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?