Clarifo

get_company_snapshot

Read-onlyIdempotent

Get a compact snapshot of a COMPANY: key financials, profile summary, entity classification, and latest filings — in a single call.

Use this as the quick entry point for company-level questions. For a deeper dossier that also searches filing content, use research_company. For deeper single-aspect dives, follow up with get_financial_statement, search_filing_content, or get_revenue_geography. NOTE: this is unrelated to get_filing_snapshot, which resolves a page_id into a source URL.

Args: company: Company name or ticker (e.g. "Apple", "AAPL"). years: Number of recent years for financials (default 3). identifier: Alias of company (accepted for client tolerance). ticker: Alias of company (accepted for client tolerance). name: Alias of company (accepted for client tolerance). company_id: Instead of a name, the company's id as portfolios returns it ("us-F" for a US issuer, "157" for a Nordic company). Wins over company and cik. cik: Instead of a name, a US issuer's SEC CIK ("37996").

Returns: { "company_name": "Apple Inc.", "display_name": "Apple Inc.", "resolution": {"input": "AAPL", "resolved_name": "Apple Inc.", "market": "us", "ticker": "AAPL", "cik": "0000320193", "confidence": 1.0, "source": "ticker_exact"}, "market": "us", "ticker": "AAPL", "entity_type": "operating", "financials": { ... }, "profile_summary": "...", "latest_filings": [ ... ], "stock_price": { "ticker": "AAPL", "price": ..., "currency": "USD", "trading_date": "...", "source": "...", "freshness_status": "live|recent|stale", "is_usable_for_live_quote": true, "age_trading_days": 0 } }

US issuers no longer listed also carry ``listing_status``
(``"delisted"`` / ``"deregistered"``), ``listing_status_date`` and
``listing_status_form`` (e.g. ``"25-NSE"``, ``"15-12G"``); the keys
appear only when set.

``stock_price`` is the most recent close from Clarifo's local
price stores (delayed, typically T-1) and is attached whenever one
exists — check ``freshness_status`` before presenting it as
current. For an explicitly live/refreshed quote, follow up with
``get_stock_price`` (optionally ``require_live=true``); for a
price chart, ``get_stock_price`` with ``days=N``.

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": "get_company_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`cik`	No
`name`	No
`years`	No
`ticker`	No
`company`	No
`company_id`	No
`identifier`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: stock_price is delayed from local stores, freshness_status should be checked before presenting as current, listing_status keys appear only when set, and company_id takes precedence over company and cik. These details materially affect interpretation of results.

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 purpose and usage guidance are front-loaded and efficient, but the large Returns JSON example is somewhat redundant given the output schema. The prose caveats about stock_price and listing_status earn their place, though the return block could be trimmed.

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 seven-parameter company lookup with an output schema and rich annotations, the description is complete: it covers purpose, routing to alternatives, every parameter, resolution precedence, output caveats, and follow-up options. Nothing an agent needs in order to call it correctly is missing.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by documenting all seven parameters, including aliases for company, default years, company_id format examples, cik semantics, and precedence rules. This adds substantial meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get a compact snapshot of a COMPANY' with the exact contents listed. It also explicitly distinguishes itself from research_company, get_financial_statement, search_filing_content, get_revenue_geography, and get_filing_snapshot.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance as the 'quick entry point for company-level questions' and names alternatives for deeper dossiers and single-aspect follow-ups. It also warns that this tool is unrelated to get_filing_snapshot, which prevents a likely confusion.

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

All Clarifo tools Inspect

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.