Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

company_facts__dossier_batch

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/batch

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": {
      "company": "<company>"
    },
    "name": "company_facts__dossier_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany name or ticker, e.g. 'Apple Inc' or 'AAPL'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
+  "description": "Company name or ticker, e.g. 'Apple Inc' or 'AAPL'",
+  "type": "string"
+}
    • removedInput schema / properties / enddt
      Removed value: -{
-  "description": "End date YYYY-MM-DD",
-  "type": "string"
-}
    • removedInput schema / properties / forms
      Removed value: -{
-  "description": "Comma-separated form types, e.g. 10-K,8-K",
-  "type": "string"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Max results (default 10, max 40)",
-  "type": "integer"
-}
    • removedInput schema / properties / q
      Removed value: -{
-  "description": "SEC EDGAR full-text query; quote phrases, e.g. \"going concern\"",
-  "type": "string"
-}
    • removedInput schema / properties / startdt
      Removed value: -{
-  "description": "Start date YYYY-MM-DD",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "q"
-]New value: +[
+  "company"
+]
  2. Added

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does supply real operational context: the price, the x402/USDC-on-Base payment rail, the location of the payment field, free previews, and the HTTP GET endpoint. What it omits is behavior on payment failure, rate limits, and why the payment field lives in params._meta when the input schema declares no such property.

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 data-source list is front-loaded and efficient, but the pricing is stated twice ('$0.01 per call in USDC on Base' appears both standalone and again with the eip155:8453 detail), and 'Free previews available' is vague filler. The raw endpoint URL at the end adds little for an agent already invoking the tool.

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, no-output-schema tool the description should say roughly what the response looks like and resolve the single-vs-batch ambiguity in its own name. It covers the inputs and sources adequately and documents payment, but leaves the batch semantics and return shape for the agent to guess.

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 100% and the single parameter already documents 'company name or ticker' with examples, so the description cannot add much. It does imply that the input is resolved into an identity and then fanned out across filings, sanctions, and domain lookups, which is mildly useful, but no format or ambiguity rules (ticker vs legal name, ambiguity handling) are given.

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 the resource and enumerates the concrete data sources covered (SEC EDGAR identity/filings, full-text search, OFAC SDN + EU sanctions, RDAP, DNS), so an agent knows exactly what comes back. It does not, however, distinguish itself from close siblings such as company_facts__dossier or company_facts__lookup_batch, and the 'batch' in the name is left unexplained against a schema that takes a single company string.

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 statement of when to choose this over company_facts__dossier, company_facts__lookup, or the other *_batch siblings. 'In one call' hints at aggregation but never says whether that means multiple data sources or multiple companies, which is exactly the decision an agent needs to make here.

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

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