Skip to main content
Glama

AI company brief: identity, SEC, sanctions, domain risk

company_brief
Read-only

Company due-diligence brief for a domain, name or ticker: Wikidata and GLEIF identity (legal name, LEI, HQ country, website, founding), SEC EDGAR ticker, CIK, periodic filings, 8-K events (last 180 days), XBRL revenue, net income, assets and cash copied from source, OFAC sanctions screening, domain registration and risk flags. Overview and risk notes are AI-generated by Anthropic Claude from that data and the homepage text; not investment or legal advice. Sources listed. Price: $0.04 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_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name, 2 to 100 characters, e.g. Apple Inc. Matched against Wikidata labels and GLEIF legal names.
domainNoCompany website domain or URL, e.g. apple.com. At least one of domain, name or ticker is required; they can be combined.
tickerNoUS stock ticker from the SEC company tickers list, e.g. AAPL or BRK.B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds substantial context beyond them: $0.04 per successful call paid in USDC via x402 v2, no charge for failed or no-match calls, sources listed, and figures copied verbatim from source rather than computed. It also discloses that the overview and risk notes are AI-generated by Anthropic Claude from the data plus homepage text. That is strong disclosure, though the run-on packaging blurs some of it (see conciseness).

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?

The content list is front-loaded and dense, with pricing, disclaimers, and the no-argument behavior trailing. Almost every clause carries information an agent needs, but the AI-generation caveat appears twice ('AI-generated by Anthropic Claude' and 'AI-generated answer'), and the single long sentence chain makes the payment and example-answer rules easy to miss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-required-parameter, read-only tool with no output schema, the definition covers the key gaps: what sources feed the brief, what fields come back (identity, filings, financials, sanctions, domain risk), that narrative sections are model-generated, and the billing model. Nothing an agent needs in order to call it correctly or set expectations is missing.

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 the schema already documents all three parameters, including the 'at least one of domain, name or ticker is required' constraint and matching behavior. The description restates the accepted input modes without adding syntax, format, or precedence rules (e.g., what happens when a domain and ticker resolve to different companies). Baseline 3 applies when the schema does the heavy lifting.

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 a concrete deliverable (company due-diligence brief) and enumerates precisely what it aggregates: Wikidata/GLEIF identity, SEC EDGAR ticker/CIK/filings, 8-K events over 180 days, XBRL figures, OFAC screening, and domain risk. It is unambiguous what the tool produces. It does not, however, distinguish itself from nearby siblings such as company_brief_pro or company_profile, leaving the agent to infer which brief to pick.

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?

Usage is implied by the accepted input types (domain, name, ticker) and the note that they can be combined, and it discloses that a no-argument call returns a stored example without a model call. What is missing is routing guidance versus the many overlapping siblings (company_brief_pro, company_profile, compliance_sanctions, sec_events). The pricing note also implicitly warns that real queries cost money, but no explicit when-not-to-use condition is stated.

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