Skip to main content
Glama
QuantLedger 73-Engine CPA, FASB GAAP, IRC Tax, Valuation & SEC 10-K MCP Server

QuantLedger 73-Engine CPA, FASB GAAP, IRC Tax, Valuation & SEC 10-K MCP Server

Official

Audit Public Company Live SEC Form 10-K Covenants, QoE & Tariffs (Cloud REST)

analyze_sec_credit_covenants_and_tariffs
Read-onlyIdempotent

Audits live SEC 10-K XBRL and footnotes to extract verified debt covenants, EBITDA bridges, Altman Z-Scores, tariff shocks, and DSCR for credit risk analysis.

Instructions

Audits any public company live SEC EDGAR Form 10-K XBRL + footnotes via QuantLedger REST API (requires RAPIDAPI_KEY): extracts character-for-character verified debt covenants, GAAP-to-Adjusted EBITDA bridge, Altman Z-Score, 19 U.S.C. 1401a tariff shock, and Base/Stress DSCR.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker_or_cik": "<ticker_or_cik>"
    },
    "name": "analyze_sec_credit_covenants_and_tariffs"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticker_or_cikYesUS stock ticker (e.g. CAT, DE, AAPL, MSFT) or 10-digit SEC CIK.
analysis_focusNoOptional focus lens (auto, credit_covenants, qoe_ebitda, tariff_1401a).auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them by disclosing the RAPIDAPI_KEY authentication requirement and the fact that data is pulled live from EDGAR rather than cached. It omits rate limits, latency, and cost implications of live calls, which keeps it from 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?

A single sentence with the verb and resource front-loaded, followed by a colon list of deliverables — nothing is wasted and the structure is easy to scan. The list is dense with jargon and acronyms, which slightly raises parsing cost, but each item carries information.

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?

For a read-only analysis tool with no output schema, the enumeration of returned analyses does the job of telling the agent what comes back. The key prerequisite is stated, and annotations cover safety. Remaining gaps — response structure, behavior on invalid tickers or missing XBRL, and how analysis_focus changes output — are modest but real.

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% with only two parameters, both documented in the schema, so the baseline of 3 applies. The description does not reference ticker_or_cik or the analysis_focus lenses (credit_covenants, qoe_ebitda, tariff_1401a) at all, so it adds no meaning beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description names a specific verb ('Audits') and a specific resource ('live SEC EDGAR Form 10-K XBRL + footnotes') and enumerates the artifacts produced (covenants, EBITDA bridge, Altman Z-Score, tariff shock, DSCR). That is far more concrete than the sibling tools' domains (statutory rates, math engine, taxonomy), so an agent can route here for 10-K credit analysis without opening the schema. It stops short of a 5 only because sibling differentiation is implicit in the domain rather than explicitly stated.

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?

The phrase 'any public company' implies scope and the parenthetical states a hard prerequisite (RAPIDAPI_KEY), which is genuine usage guidance. However, there is no statement of when to prefer this tool over the math engine or statutory-rates siblings, and no exclusions such as non-US filers or companies without 10-K XBRL.

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