Operational KPI Drivers

Research filing narrative and markdown tables for operational KPI values and driver context.

When To Use It

Use these tools for operational metrics that are not consistently modeled as standard XBRL financial concepts.

Request Example

This is an MCP-only tool. Call it through an MCP client after configuring edgar-mcp.

{
  "tool": "get_operational_kpi_drivers",
  "arguments": {
    "ticker": "AAPL",
    "year": 2025,
    "quarter": 4,
    "topic": "example_topic"
  }
}

Response Fields To Inspect

• Driver name, value, units, period, and source evidence before using a KPI in an answer.
• Coverage or provenance fields when a KPI comes from narrative disclosures.
• Directional and period-comparison fields before describing a trend.

Errors And Coverage

• 401 or 403: the API key is missing, expired, or not allowed to use this tier.
• 429: retry after the rate-limit window, and prefer broader batch or series tools over repeated single-period calls.
• Paid or LLM-backed paths should be used only when cheaper fact, filing, table, or text tools cannot answer the question.
• Treat partial coverage, empty arrays, and warning fields as answer-quality signals even when HTTP status is 200.

Related Tools

Operational KPI Driver Rows, Filing Document, Filing Evidence, Search Extractions

Generated Reference

Contract

MCP Signature