Skip to main content
Glama

Reported financials from SEC filings

company_financial_facts
Read-onlyIdempotent

Plumbline: Reported values of one XBRL concept for one SEC filer, by CIK or ticker, from its SEC filings (EDGAR): each value with its period, fiscal year, form, filing date and accession number, the latest 40.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK; or give ticker
tickerNoStock ticker of an SEC filer, such as AAPL
conceptNoXBRL concept name, default Revenues; others include RevenueFromContractWithCustomerExcludingAssessedTax, NetIncomeLoss, Assets
taxonomyNoDefault us-gaap

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cik / description
      Added value: +"SEC CIK; or give ticker"
    • addedInput schema / properties / concept / description
      Added value: +"XBRL concept name, default Revenues; others include RevenueFromContractWithCustomerExcludingAssessedTax, NetIncomeLoss, Assets"
    • addedInput schema / properties / taxonomy / description
      Added value: +"Default us-gaap"
    • addedInput schema / properties / ticker / description
      Added value: +"Stock ticker of an SEC filer, such as AAPL"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuine behavioral context beyond them: the result is capped at the latest 40 observations and each value carries its period, fiscal year, form, filing date and accession number. It does not state ordering guarantees or what happens when fewer than 40 facts exist, which keeps it short of a 5.

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?

One dense sentence, front-loaded with what is returned, followed by the per-value fields and the 40-item cap — every clause carries information. The only waste is the 'Plumbline:' vendor prefix, which occupies prime position without helping selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the returned fields (period, fiscal year, form, filing date, accession number) and the 40-result cap, which is what an agent needs to decide whether this tool answers its question. Remaining gaps are edge behavior such as no-match handling and whether the 40 limit applies per concept.

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 the schema already documents cik, ticker, concept and taxonomy including the Revenues default and example concepts. The description reinforces the CIK-or-ticker choice and the single-concept scope but adds no format, synonym or substitution detail beyond the schema. Baseline 3 applies.

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: reported values of one XBRL concept for one SEC filer from EDGAR filings, keyed by CIK or ticker. The unit of retrieval (one concept, one filer) is explicit, so an agent knows exactly what a single call returns. Siblings (convert_document, screen_sanctions, etc.) are unrelated domains, so no differentiation is needed.

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?

Usage is implied by the framing — call this when you need a filer's reported XBRL values — but there is no explicit when-to-use versus alternative, no note that a different concept or filer requires a separate call, and no mention of what to do if the ticker/CIK is ambiguous or missing. The 'latest 40' constraint hints at the boundary of coverage but is not framed as guidance.

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