Skip to main content
Glama

AI company brief from 10-K risk factors, 8-Ks and XBRL

company_brief_pro
Read-only

AI company research brief from SEC filings: the latest 10-K (business, risk factors, MD&A), recent 8-Ks and XBRL financials. Returns business model, segments, competitive position, key risks each with a verbatim 10-K quote checked in code and an EDGAR link, recent developments, watch items, and a financial snapshot copied from XBRL. Lookup by ticker, name, domain or LEI. AI-generated by Anthropic Claude; companies without a 10-K get a profile and website-only brief. Price: $0.25 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_pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNo20-character Legal Entity Identifier (ISO 17442, check digits verified), e.g. HWUPKR0MPOU8FGXBT394.
nameNoCompany name, 2 to 100 characters, e.g. Apple Inc. Matched against Wikidata labels, GLEIF legal names and SEC titles.
domainNoCompany website domain or URL, e.g. apple.com (matched to the Wikidata official website).
tickerNoUS stock ticker from the SEC company tickers list, e.g. AAPL or BRK.B. At least one of ticker, name, domain or lei is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses pricing ($0.25 per successful call in USDC via x402 v2), that failed and no-match calls are not charged, that output is AI-generated by Anthropic Claude, that risk quotes are verbatim and code-checked with EDGAR links, and that a zero-argument call returns a cached example without a model invocation. These are exactly the cost and side-effect facts an agent needs before spending money.

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?

Front-loaded with purpose and outputs, then cost, then the AI-generated/no-argument caveats — a sensible priority order. It is a dense block of several sentences with pricing detail, but each sentence contributes a distinct fact rather than repeating the schema.

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 read-only, open-world research tool with no output schema, the description fully enumerates the returned sections (business model, segments, competitive position, quoted risks, developments, watch items, XBRL snapshot), the coverage limitation for non-10-K companies, and the billing model. Nothing material is left for the caller to discover by trial.

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 each parameter already documents its format and matching source, so the schema carries the weight. The description only restates the four lookup keys, adding no format or precedence detail (e.g., what happens if both ticker and name are supplied) beyond the structured fields — the baseline 3.

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?

States a specific verb and resource ('AI company research brief from SEC filings'), then enumerates the source material (10-K business/risk factors/MD&A, 8-Ks, XBRL) and the output contents. An agent knows exactly what this produces. It does not, however, contrast itself with the similarly named siblings (company_brief, company_profile, research_brief), so selection among them still requires inference.

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?

'Lookup by ticker, name, domain or LEI' establishes the input context, and the description notes the fallback for companies without a 10-K. But there is no explicit when-to-use/when-not guidance and no routing to alternatives such as sec_filings or company_profile, so a caller cannot tell from the text why it should pick this tool over its near-namesakes.

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