Skip to main content
Glama

company_facts__seller_screen

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…[20 more chars, already applied] 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/seller-screen

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

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. Added

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 does carry real weight here: it discloses a paid model ($0.01 per call in USDC on Base eip155:8453, x402 payment via params._meta["x402/payment"]) and the HTTP endpoint, which are non-obvious operational facts. It does not say what happens on missing or failed payment, how a partial-source failure is handled, or what the aggregated response contains.

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 capacity list is front-loaded and efficient, but the price is stated twice in near-identical form ('$0.01 per call in USDC on Base' and then again with the chain ID and x402 details), and the truncated 'Free…' fragment adds noise. Roughly a third of the text is redundant or garbled.

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 composite tool with no output schema, the description enumerates inputs to the aggregation but says nothing about the shape or structure of the combined result, so an agent cannot anticipate how to read a response spanning four sources. Payment mechanics are covered, but the multi-source return contract is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema description coverage, including an example ('Apple Inc' or 'AAPL'). The description adds nothing beyond the schema about the company input, so the baseline of 4 applies for a one-parameter tool.

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 underlying sources: SEC EDGAR identity/filings and full-text search, OFAC SDN and EU sanctions screening, RDAP domain facts, DNS. That is a concrete composite-screening purpose. It stops short of contrasting itself with siblings like company_facts__dossier or check_sanctions__screen, so it does not fully distinguish itself.

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?

The name and the source list imply a pre-transaction seller due-diligence use case, but the description never states when to use this composite versus the narrower sibling tools. There are no exclusions, prerequisites, or decision rules for an agent that also sees company_facts__risk, dossier, and check_sanctions__seller.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources