Skip to main content
Glama

get_company_profile

Full enriched profile for ONE company (mirrors the /company/{ticker} page): name, ticker, sector, the LLM business summary + one-line pitch, key fundamentals (price + as-of date, market cap, margins, ROE/ROA, valuation), dividend facts, competitors, plus its latest SEC filings — the DATED evidence you cite. May also include insider_cluster_buying: a dated open-market cluster-buy DISCLOSURE fact (≥3 distinct insiders each buying, SEC code P, within a 30-day window; disclosed Form 4 activity, not a prediction or buy signal; only when one qualifies). May also include sector_percentiles: where the company's metrics (P/E, margins, ROE, growth, yield, absolute FCF) sit relative to covered peers in the same sector, each with a summary + peer count + as-of date (a relative position, not a valuation/quality judgment; only when rankable). May also include long_term_picture: business quality, price vs fundamentals, long-run trend and cash returned as x/10 from the published Top 10 pillars, with a summary sentence (a published formula, not advice). May also include valuation_context: today's P/E, P/S, P/FCF against the company's own fiscal-year range and a reverse DCF's implied free-cash-flow growth (a simple model, not a price target). May also include dividend_safety: a single-fiscal-year dividend-coverage assessment from SEC XBRL (earnings + free-cash-flow payout ratios; outcome supported/stretched/not_assessable/stale_dividend_data; past coverage, not a forecast; only when the company paid a dividend). stale_dividend_data means the latest fiscal year with a reported dividend payment is OLDER than the latest year of reported accounts (latest_financials_fiscal_year), so no ratio is given — do not infer from it that the dividend was cut, nor that the data is missing. May also include filing_changes: an AI-assisted, source-bounded comparison of the two most-recent same-form SEC filings (Risk Factors / MD&A additions, removals, wording changes) with each side's filed date + SEC url — a source comparison, not a materiality/legal/investment conclusion; only when a cached diff exists. May also include institutional_ownership: dated SEC Form 13F-HR holdings — the count of distinct investment managers reporting this security at the latest quarter-end plus a derived between-quarters position-change count (quarter-end snapshots filed within 45 days, not real-time; a reported holdings change, never a same-day trade; only when 13F data exists). May also include short_interest: reported FINRA equity short interest (shares) as of the latest settlement date, with the source-reported change + days-to-cover (delayed, bi-monthly; not real-time, not a percent of float, not a squeeze signal; only when short-interest data exists). May also include signal_agreement: how many standard chart readings are currently in a bullish vs bearish state for this company — bullish.count / bearish.count with the member signals as { key, note }, neutral, and computable, the number of signals we could actually compute for it. ALWAYS cite the count against computable ("6 of 9"): a company with a short price history has no 200-day average and is scored out of fewer signals, so a bare count is not comparable across companies. Describes past price behaviour only — never a buy/sell signal (only when computable signals exist). May also include next_earnings_date — which never travels alone: next_earnings_is_estimate says what KIND of date it is (1 = the data source's own ESTIMATE, 0 = a confirmed/announced date, null = unknown), and next_earnings_as_of says when it was last refreshed. State the kind whenever you cite the date — an estimated date is "expected around", never "reports on". Dates are refreshed in rotation, so a date at or before its next_earnings_as_of stamp may have moved since we read it; treat it as the date we hold rather than as settled. next_earnings_date is always today or later: a date that has already passed is withheld. next_earnings_status says which case you are in — "upcoming" means we hold a forward date; "passed" means our calendar's last expected date has gone by, and that date is carried in last_expected_earnings_date for context only. Never present last_expected_earnings_date as upcoming, and never read it as confirmation that the company reported — only last_earnings below is a filed fact. May also include last_earnings — the OPPOSITE KIND of date: the day the company filed its earnings announcement with the SEC (Form 8-K, Item 2.02). It is BACKWARD-looking and is a FILED FACT, never an estimate, so never present it as upcoming and never mix it with next_earnings_date without saying which is which. When its stale flag is true the announcement is over two quarters old — call it the most recent one IN OUR DATA rather than implying the company reported recently. When date is null, reason says why and the difference matters: foreign_private_issuer means the company reports on Form 6-K, which carries no earnings item code, so we hold no confirmed date — a coverage boundary, NOT a claim that it has not reported. Never substitute another filing or date for a missing one. Identify by ticker (preferred) or name. Returns an error object if the company is NOT in the covered universe. Universe: US public companies: S&P 500 + NASDAQ-100 + Dow Jones + Russell 1000 + Russell 2000 (deduped — effectively the Russell 3000 plus the Dow), spanning large-, mid-, AND small-cap companies, plus the major US exchange-traded funds (ETFs). UK public companies: the FTSE 350 (FTSE 100 + FTSE 250), listed on the London Stock Exchange. Data: SEC EDGAR filings + market-data fundamentals, each figure dated. Informational only, NOT financial advice.

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

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name (used if ticker is unknown).
tickerNoTicker, e.g. NVDA (preferred).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so extensively: it discloses optional-field conditions, dated evidence, SEC-source caveats, stale-data semantics, the difference between estimated and filed earnings dates, and error behavior for out-of-universe companies. It also clearly marks derived fields as non-predictive and non-advice, which is meaningful behavioral context beyond a bare schema.

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 purpose is front-loaded, and the repeated 'May also include' structure helps organize many optional fields. Still, the description is extremely long with dense defensive caveats, and some of it could be trimmed or bulleted for faster agent parsing without losing essential meaning.

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?

Given the absence of an output schema and annotations, the description is complete enough to explain the return contents, conditional fields, source boundaries, and error cases. It also documents the covered universe and identification rules, which an agent needs to invoke the tool correctly.

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 description coverage is 100%, so both parameters are already documented in the input schema. The description reinforces that ticker is preferred and name is a fallback, but adds no new syntax or format detail beyond what the schema provides, matching the baseline of 3 for high-coverage schemas.

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 opening sentence states a specific verb and resource: 'Full enriched profile for ONE company (mirrors the /company/{ticker} page).' It lists the included content categories, making clear this is a single-company profile rather than a search or comparison tool. The 'ONE company' scope implicitly distinguishes it from compare_companies and search_companies.

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 description explains how to identify the company (ticker preferred, name acceptable), the covered universe, and that an error object is returned if the company is not covered. However, it does not explicitly state when to use this tool instead of compare_companies or search_companies, so alternative-selection guidance is only implied.

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