Skip to main content
Glama

AI company due-diligence report: KYB, ownership, risk

company_report
Read-only

AI KYB and vendor due-diligence report on a company from its domain, name or US ticker: identity, GLEIF ownership (parents, subsidiaries), business, SEC XBRL financials copied from filings, recent 8-K events, domain registration, email DNS, website security headers and OFAC screening of the entity and related companies, plus risk ratings, red flags and open questions, quotes checked against cited sources. Written by Anthropic Claude; takes 1-2 minutes; not investment advice. Price: $0.75 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged. AI-generated answer; a call with no arguments returns the stored example answer without a model call.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key (1 to 10 digits) instead of ticker; needs domain or name as well.
nameNoCompany name, 2 to 100 characters, e.g. Apple Inc. Matched to Wikidata labels and GLEIF exact legal names.
domainNoCompany website domain or URL, e.g. apple.com. Matched to Wikidata and GLEIF, and used for registry RDAP, email DNS and a live HTTPS security-header check. Give domain, name or ticker.
tickerNoUS stock ticker for SEC EDGAR filings and XBRL financials, e.g. AAPL. When omitted, a US listing on Wikidata whose SEC registrant name matches is used. Mutually exclusive with cik.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Far beyond the readOnlyHint/openWorldHint annotations, it discloses the payment model (USDC via x402 v2), what is and is not billed, expected latency, that output is AI-generated with quotes checked against cited sources, that it is not investment advice, and that entity plus related companies are screened against OFAC. That is exactly the cost, latency and caveat information an agent needs before committing.

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 and every subsequent clause carries information — coverage list, author, latency, pricing, billing exceptions, the no-arg behavior. The coverage enumeration is long and run-on, and could be trimmed or bulleted, but it is not padding.

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?

With no output schema, the description does the necessary work by naming the report's contents, including risk ratings, red flags and open questions, plus the example-answer fallback. Only the concrete output format (structure/markdown vs. fields) is left unspecified, a minor gap for a report-generation tool.

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%, so each of the four parameters is already documented, including cik/ticker mutual exclusivity and what domain is used for (RDAP, email DNS, HTTPS header check). The description only restates the accepted input kinds ('from its domain, name or US ticker') and adds no new format or precedence detail, so the 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 opens with a specific verb and resource — an 'AI KYB and vendor due-diligence report on a company' — and enumerates exactly what it covers (identity, GLEIF ownership, SEC XBRL financials, 8-K events, DNS/headers, OFAC screening, risk ratings). It is clearly a deep composite report, which implicitly distinguishes it from shallow siblings like company_brief, but it never names or contrasts those siblings explicitly.

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

Usage Guidelines4/5

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

It gives real operational context for the decision to call: 1-2 minutes runtime, $0.75 per successful call vs free failures/no-match, and the zero-argument shortcut that returns a stored example without a model call or charge. What is missing is any explicit when-to-use/when-not guidance relative to alternatives such as company_brief, company_profile or company_brief_pro.

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