Skip to main content
Glama

Compare one XBRL concept across all companies

edgar_get_concept_across_companies
Read-onlyIdempotent

Get one XBRL concept for a calendar period across every SEC filer that reported it to screen and compare peers by value; supports sorting, filtering, and paging.

Instructions

Cross-company query: get one XBRL concept (e.g. Revenues, Assets, NetIncomeLoss) for one calendar period for every SEC filer that reported it, using the SEC frames API. Sortable and paged. Use for screening and peer comparison ("largest companies by total assets at end of 2023", "net income of all filers in CY2023"). For one company's history use edgar_get_company_facts. Period format: "CY2023" (annual duration), "CY2023Q2" (quarterly duration), "CY2023Q4I" (instant, for balance-sheet items like Assets). Unit e.g. "USD", "USD-per-shares", "shares", "pure". Behavior: free, read-only GET to data.sec.gov (no token). Returns paged {count,total,offset,hasMore,nextOffset,meta:{taxonomy,concept,label,unit,period,source_url},items:[{rank,cik,entity_name,value,start,end,location,accession_number}]}. Optional ciks filter restricts to given companies. Errors: NOT_FOUND (no such concept/unit/period frame), SEC_FETCH_FAILED. WHEN NOT TO USE: for one company's time series use edgar_get_company_facts; for filings use edgar_list_filings. COST: free - direct sec.gov requests from this MCP server, no APIFY_TOKEN, no Apify billing. PARAMETERS: period must match the concept type: flow items (Revenues, NetIncomeLoss) use durations "CY2023" or "CY2023Q2"; balance-sheet items (Assets, Liabilities, StockholdersEquity) need an instant such as "CY2023Q4I" - the wrong kind returns NOT_FOUND. Calendar periods are SEC-aligned approximations of each filer's fiscal period. concept, unit and taxonomy are case-sensitive path parts of one SEC frame, so all three must exist together: EPS uses unit "USD-per-shares", share counts "shares", ratios "pure"; dei concepts (e.g. EntityCommonStockSharesOutstanding) need taxonomy "dei". companies filters the frame after download (any ticker/CIK/name; unresolvable entries are silently skipped); rank is computed after that filter and the chosen sort, so rank 1 = largest value among the kept companies with value_desc. limit/offset then page the ranked rows. EXAMPLE: {"concept":"Assets","period":"CY2023Q4I","limit":10} -> top 10 filers by total assets at end of 2023.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOptional, one of "value_desc" | "value_asc" | "name", default "value_desc" (largest first); "name" = entity name A-Zvalue_desc
unitNoOptional, default "USD". Case-sensitive unit of measure: "USD", "USD-per-shares" (EPS), "shares", "pure" (ratios), or another currency code such as "EUR"USD
limitNoOptional page size: items to return, integer 1-500 (default 25). Example: 10
offsetNoOptional zero-based number of items to skip, integer >= 0 (default 0); pass nextOffset from the previous response, e.g. 20
periodYesRequired. Calendar frame, pattern ^CY\d{4}(Q[1-4]I?)?$: "CY2023" = annual duration, "CY2023Q2" = quarterly duration, "CY2023Q4I" = instant at quarter end (balance-sheet items)
conceptYesRequired. Exact XBRL concept name, case-sensitive, e.g. "Assets", "Revenues", "NetIncomeLoss"
taxonomyNoOptional, default "us-gaap". One of "us-gaap", "ifrs-full", "dei", "srt"us-gaap
companiesNoOptional, default omitted = all filers. 1-50 tickers, CIKs or name fragments to keep. Example: ["AAPL","MSFT","GOOGL"]

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNoTool-specific context (company, source_url, ...)
countYesNumber of items in this page
itemsYesResult rows for this page
totalYesTotal items matching the filters (before paging)
offsetYesOffset of the first item in this page
hasMoreYesTrue if more items exist after this page
nextOffsetYesOffset to pass for the next page, or null

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.2.2
    • changedInput schema / properties / companies / description
      Previous value: -"Optional tickers/CIKs/names to restrict results to"New value: +"Optional, default omitted = all filers. 1-50 tickers, CIKs or name fragments to keep. Example: [\"AAPL\",\"MSFT\",\"GOOGL\"]"
    • changedInput schema / properties / concept / description
      Previous value: -"Exact concept name, case-sensitive, e.g. \"Assets\", \"Revenues\", \"NetIncomeLoss\""New value: +"Required. Exact XBRL concept name, case-sensitive, e.g. \"Assets\", \"Revenues\", \"NetIncomeLoss\""
    • changedInput schema / properties / limit / description
      Previous value: -"Optional page size: items to return, integer 1-500 (default 25)"New value: +"Optional page size: items to return, integer 1-500 (default 25). Example: 10"
    • changedInput schema / properties / offset / description
      Previous value: -"Number of items to skip for paging (default 0); use nextOffset from the previous response"New value: +"Optional zero-based number of items to skip, integer >= 0 (default 0); pass nextOffset from the previous response, e.g. 20"
    • changedInput schema / properties / period / description
      Previous value: -"\"CY2023\", \"CY2023Q2\" or \"CY2023Q4I\" (instant)"New value: +"Required. Calendar frame, pattern ^CY\\d{4}(Q[1-4]I?)?$: \"CY2023\" = annual duration, \"CY2023Q2\" = quarterly duration, \"CY2023Q4I\" = instant at quarter end (balance-sheet items)"
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order (default value_desc)"New value: +"Optional, one of \"value_desc\" | \"value_asc\" | \"name\", default \"value_desc\" (largest first); \"name\" = entity name A-Z"
    • changedInput schema / properties / taxonomy / description
      Previous value: -"Taxonomy (default \"us-gaap\"; also \"ifrs-full\", \"dei\", \"srt\")"New value: +"Optional, default \"us-gaap\". One of \"us-gaap\", \"ifrs-full\", \"dei\", \"srt\""
    • changedInput schema / properties / unit / description
      Previous value: -"Unit of measure (default \"USD\"; e.g. \"USD-per-shares\", \"shares\")"New value: +"Optional, default \"USD\". Case-sensitive unit of measure: \"USD\", \"USD-per-shares\" (EPS), \"shares\", \"pure\" (ratios), or another currency code such as \"EUR\""
  2. Addedv1.2.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/openWorld/destructive, but the description adds real context beyond them: endpoint (data.sec.gov), no token required, zero cost, named error codes (NOT_FOUND, SEC_FETCH_FAILED), and the paged response envelope. This goes well past what annotations declare.

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 purpose and organized under clear labels (Period format, Behavior, WHEN NOT TO USE, COST, PARAMETERS, EXAMPLE). It is long and repeats the period-format and free/no-token facts in two places, which costs a little against strict conciseness.

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 an 8-parameter, open-world cross-company query it covers period semantics, unit rules, filtering/paging behavior, error codes, cost, and a worked example. With an output schema present, the return envelope need not be fully explained, so nothing essential 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?

Schema coverage is 100% (baseline 3), yet the description adds substantial semantics the schema lacks: instant-vs-duration period rules per concept type, the interdependence of case-sensitive concept/unit/taxonomy, unit selection by concept (USD-per-shares, shares, pure), and companies-as-post-filter behavior with rank recomputation.

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: retrieve one XBRL concept across every SEC filer via the Frames API. It explicitly contrasts with edgar_get_company_facts for single-company history, so the agent can distinguish it from siblings without opening schemas.

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?

Gives concrete use cases (screening, peer comparison, with quoted example queries) and an explicit WHEN NOT TO USE section routing to edgar_get_company_facts and edgar_list_filings. When-to-use and when-not-to-use are both stated directly.

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