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

Search & Inspect 73 CPA, GAAP, IRC Tax & Credit Blueprints (Keyless Local)

list_institutional_math_suites_73
Read-onlyIdempotent

Search and inspect 10 institutional suites and 73 deterministic accounting, tax, valuation, and compliance blueprints to retrieve governing statutes, required input datasets, and output schedules.

Instructions

Runs locally with no API key required. Searches and inspects all 10 Institutional Suites and 73 deterministic CPA, FASB GAAP, IRC Tax, 409A Valuation, GovCon DCAA, CMS Medicare, CRE, M&A QoE, Customs, and Credit blueprints (BI-01 to BI-73, 292 laws), returning governing statutes, required input datasets, and output schedules.

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

Input Schema

NameRequiredDescriptionDefault
keywordNoOptional statute or topic search keyword (e.g. ASC 842, 382, UBIT, DCAA, ERISA).
suite_idNoOptional suite-01 through suite-10 filter.
engine_codeNoOptional exact code (BI-01..BI-73) to inspect full schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered by structured data. The description adds genuinely useful operational context — "Runs locally with no API key required" — plus a list of what is returned (statutes, datasets, schedules), which matters given there is no output schema. It stops short of stating result limits, pagination, or whether filters combine.

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?

Two sentences, front-loaded with the most decision-relevant fact (local, no API key), followed by scope and return contents. The long domain enumeration is dense but each term adds disambiguation value; nothing is redundant filler.

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 zero-required-parameter, three-optional-parameter read tool with no output schema, the description supplies the return shape (statutes, input datasets, output schedules) and the deployment constraint. Remaining gaps — filter combination behavior and result-set size — are minor rather than blocking.

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 keyword, suite_id, and engine_code each documented and exemplified (ASC 842, 382, UBIT, DCAA, ERISA), so the schema carries the parameter burden. The description only echoes that keyword search and code inspection exist, without adding format details or explaining how the three filters interact. Baseline 3 applies.

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?

Uses specific verbs ("Searches and inspects") and a precisely scoped resource (10 suites, 73 blueprints BI-01..BI-73), with the domains enumerated. It does not, however, contrast itself with the sibling execute_institutional_math_engine, so an agent must infer that this is the discovery/read path rather than the execution path.

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 only implied: the tool reads as a catalog/search surface you consult before executing, and the mention of "required input datasets" hints at that workflow. There is no explicit when-to-use/when-not statement, no mention of the execute sibling, and no guidance on choosing between keyword, suite_id, or engine_code lookups.

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