Skip to main content
Glama

Company profile

company_profile
Read-onlyIdempotent

Return the profile of one company: legal name, FinancialMD id, CIK, listings (ticker, exchange, currency), sector and industry, the statement template it is standardized with (for example industrial, bank, insurer), its fiscal year end, and the list of datasets available (which statements, ratios, filings, KPIs exist), the listing status (active, delisted with the date, or inactive), country and business address, former names, the newest head count with its source sentence (served only at confidence 0.90 or more) and cover-page shares per share class (never summed across classes). Call it before pulling statements to learn the template and fiscal calendar, and to confirm the identifier resolved to the right company.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "ticker:AAPL"
    },
    "name": "company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.

Output Schema

NameRequiredDescriptionDefault
dataNoProfile: fmd_id, cik, name, country, reporting_template, fiscal_year_end_month, status, sic_code, sector (SIC division), industry (SEC title of the SIC code), classification { scheme, sic_code, source_url, scheme_url } or null, listings (ticker, mic, currency, is_primary), available_datasets, updated_at, registry (sec, or esef for an EU or UK issuer), reporting_currency, accounting_standard, registrations [{ registry, local_id, id_kind, role, countries, source_url }].
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / company / description
      Previous value: -"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."
    • changedOutput schema / properties / data / description
      Previous value: -"Profile: fmd_id, cik, name, country, reporting_template, fiscal_year_end_month, status, sic_code, sector (SIC division), industry (SEC title of the SIC code), classification { scheme, sic_code, source_url, scheme_url } or null, listings (ticker, mic, currency, is_primary), available_datasets, updated_at."New value: +"Profile: fmd_id, cik, name, country, reporting_template, fiscal_year_end_month, status, sic_code, sector (SIC division), industry (SEC title of the SIC code), classification { scheme, sic_code, source_url, scheme_url } or null, listings (ticker, mic, currency, is_primary), available_datasets, updated_at, registry (sec, or esef for an EU or UK issuer), reporting_currency, accounting_standard, registrations [{ registry, local_id, id_kind, role, countries, source_url }]."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is met without description help. The description still adds real behavioral context beyond them: head count is only served at confidence ≥0.90, and cover-page shares are never summed across share classes — both are non-obvious output semantics a caller would otherwise not anticipate.

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 the core statement, then a field enumeration, then the usage instruction — a sensible order. The field list is long and partly duplicates what the output schema already conveys, so a little compression is possible, but every clause carries information.

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?

With one fully documented parameter, complete annotations, and an output schema, the description supplies everything else an agent needs: which fields come back, the confidence threshold on head count, the no-summing rule for share classes, and where this call sits in the workflow.

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 the schema itself already documents fmd_ ids, cik:, ticker: with optional MIC, bare tickers, and LEI for non-SEC filers. The description contributes only the framing that the identifier resolution should be confirmed against the returned profile, which is marginal added meaning over the 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?

Starts with a specific verb and resource ("Return the profile of one company") and then enumerates the exact fields returned — legal name, CIK, listings, sector, template, fiscal year end, dataset availability, listing status, head count, share classes. That level of specificity makes it unmistakable against siblings like fund_profile or company_lookup.

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?

Gives explicit when-to-use guidance: call it before pulling statements to learn the template and fiscal calendar, and to confirm the identifier resolved correctly. It stops short of naming an alternative for non-company entities (e.g. funds), so the routing is clear but not fully disambiguated.

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