Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

company_facts__risk

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

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__risk"
  }
}

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
  3. Removed
  4. Changed2 schema fields changed
    • removedInput schema / properties / company / description
      Removed value: -"Company name"
    • removedInput schema / properties / domain
      Removed value: -{
-  "description": "Domain (optional)",
-  "type": "string"
-}
  5. Changed2 schema fields changed
    • changedInput schema / properties / company / description
      Previous value: -"Company or entity name to screen"New value: +"Company name"
    • changedInput schema / properties / domain / description
      Previous value: -"Optional domain for registration-age signal"New value: +"Domain (optional)"
  6. Added

TDQS

B3.1/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 behavioral burden. It does disclose critical operational facts that structured fields do not: this is a paid tool ($0.01 per call in USDC on Base, eip155:8453) requiring an x402 payment blob in params._meta, plus a free preview option and an HTTP endpoint. It says nothing about error behavior when no company matches, how sanctions hits are represented, rate limits, or result shape.

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 inventory is front-loaded and useful, but the pricing sentence is repeated almost verbatim ('$0.01 per call in USDC on Base' appears twice, once again with the chain ID). That duplication wastes space in a definition that is otherwise compact. The trailing HTTP endpoint is useful but read as a raw spec dump.

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 aggregation tool with no output schema and no annotations, the description covers what categories of data come back and how payment works, which is the minimum an agent needs. It stops short of describing the response structure, the meaning of a sanctions match, or fallback behavior on no-hit, leaving real gaps for a tool that bills per 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 description coverage is 100% with a single required 'company' parameter already documented with examples ('Apple Inc' or 'AAPL'). The description adds no additional meaning about how ticker vs. legal name is resolved or how ambiguous matches are handled, so the high-coverage baseline of 3 applies.

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 concrete data sources and resources it returns: SEC EDGAR identity and filings, full-text filing search, OFAC SDN and EU sanctions screening, RDAP domain facts, and DNS. That is a specific verb-plus-resource statement an agent can act on. It does not, however, distinguish itself from close siblings such as company_facts__dossier or company_facts__risk_batch, which appear to overlap in scope.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative. The phrase 'in one call' hints that this is an all-in-one aggregation tool, but the agent is left to infer how it differs from company_facts__dossier, company_facts__filings, or company_facts__ticker. No prerequisites or exclusions are stated beyond the payment requirement.

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