Skip to main content
Glama

Sec Xbrl Get Company Facts

sec_xbrl_get_company_facts
Read-onlyIdempotent

List all XBRL taxonomies and concept tags filed by a company (CIK required). Returns entity name, taxonomy names (us-gaap, dei, etc.), concept count per taxonomy, and a sample of up to 20 tag names each. Use get_company_concept or get_company_financials to retrieve actual numeric values for a specific tag.

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": {
      "cik": "320193"
    },
    "name": "sec_xbrl_get_company_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesSEC Central Index Key (e.g., "320193" for Apple, "789019" for Microsoft)

Output Schema

NameRequiredDescriptionDefault
cikYesSEC Central Index Key as numeric value
taxonomiesYesSummary of available XBRL taxonomies
entity_nameYesLegal name of the company

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description still adds useful behavior: the response contains entity name, taxonomy names, per-taxonomy concept counts, and only a sample of 'up to 20 tag names' per taxonomy — that truncation cap is the kind of detail an agent needs to know before assuming it has the full tag list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste. The output shape is front-loaded before the disambiguation sentence, so an agent scanning the first clause already knows what it gets back.

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?

A one-parameter, read-only lookup with full schema coverage, rich annotations, and an output schema that carries return-value detail. The description covers purpose, output shape, sample truncation, and routing to siblings — 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.

Parameters3/5

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

Schema coverage is 100% and the single CIK parameter is documented with concrete examples (Apple 320193, Microsoft 789019). The description only restates 'CIK required', which the required array already conveys, adding no new meaning. 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.

Purpose5/5

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

States a specific verb and resource: 'List all XBRL taxonomies and concept tags filed by a company', plus the required identifier (CIK). It also delineates what the tool does NOT return ('actual numeric values'), which separates it cleanly from get_company_concept and get_company_financials.

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?

Explicitly routes the agent: 'Use get_company_concept or get_company_financials to retrieve actual numeric values for a specific tag.' That names alternatives and the condition that selects them. The positive case (use this tool to discover which tags exist before fetching values) is implied rather than stated, and no guidance is given relative to sec_xbrl_search_filings.

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.