Skip to main content
Glama
Sign In

EdgarStack

by com.edgarstack
OverviewDiscussionsAdmin

Audit SEC financial data coverage, provenance, and balance-sheet tie-out

assess_financial_data_quality
Read-onlyIdempotent

Check how far the SEC numbers for a company can be trusted and traced. Two checks:

  • check="coverage" (default): SEC XBRL coverage, stale line-item flags, filing accession provenance, and period-end alignment for up to 12 metrics (default revenue, netIncome, totalAssets, totalLiabilities, operatingCashFlow, capex). Annual, quarterly or TTM; limit 1–12, default 5.

  • check="balance_sheet": compares total assets with total liabilities plus total equity for exact matching annual or quarterly period ends, returning the arithmetic residual, source tags, filing accessions and missing components. Annual or quarterly only; limit 1–12, default 8. Missing facts remain unavailable rather than zero. Findings describe coverage and traceability; a residual is a review signal, not proof of an accounting error. Not financial advice.

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": "<ticker>"
    },
    "name": "assess_financial_data_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkNocoverage
limitNoObservations per metric (coverage default 5; balance_sheet default 8)
periodNoTTM is available for check=coverage onlyannual
tickerYesUS ticker symbol
metricsNocheck=coverage only: up to 12 metrics; omit for the defaults

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the description's added value is in interpretation: missing facts stay unavailable rather than being zero-filled, and a residual is a review signal rather than proof of an accounting error. That is exactly the kind of caveat an agent needs to report results responsibly. It does not mention rate limits, auth, or cost, which keeps it at 4.

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?

Purpose is front-loaded in one sentence, then two tightly scoped bullets per mode, then a short caveat block. Every line carries operative information, and the mode-specific defaults are stated where they are needed rather than scattered.

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?

With no output schema, the description carries the burden of describing returns, and it does: coverage returns coverage/staleness/provenance/period-alignment flags, balance_sheet returns residual, source tags, accessions and missing components. Against 5 parameters and two enum-driven modes, nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

Schema coverage is 80%, so the schema already documents ticker, period, limit and metrics. The description still adds real meaning the schema omits: the default metric list (revenue, netIncome, totalAssets, totalLiabilities, operatingCashFlow, capex) and the fact that limit defaults differ per check (5 vs 8). It does not explain the large metric enum or the eligibility of individual metrics.

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?

The description names a specific verb-and-resource pair ('check how far the SEC numbers for a company can be trusted and traced') and then enumerates two discrete modes, coverage and balance_sheet, each with its own subject matter. An agent can distinguish this quality-audit tool from data-fetching siblings like get_financials purely from the text.

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?

It states which check is the default ('coverage'), what each mode is for, and mode-specific constraints (TTM only for coverage; balance_sheet is annual or quarterly only), plus per-mode limit defaults. It does not explicitly route the agent away from sibling tools such as analyze_earnings_quality or compute_ratios, which is the only gap.

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

All EdgarStack toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources