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

Crosswalk 6-Digit NAICS, 4-Digit SIC & 8-Digit GICS Codes (Keyless Local)

resolve_universal_industry_taxonomy
Read-onlyIdempotent

Maps NAICS, SIC, or GICS codes and industry keywords bidirectionally to SEC Review Office classifications and applicable statutory suite recommendations.

Instructions

Runs locally with no API key required. Maps any US 6-digit NAICS (1,012), 4-digit SIC (1,184), or 8-digit GICS (163) code or industry keyword bidirectionally with SEC Review Office and applicable statutory suite recommendations.

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": {
      "code_or_keyword": "<code_or_keyword>"
    },
    "name": "resolve_universal_industry_taxonomy"
  }
}

Input Schema

NameRequiredDescriptionDefault
code_or_keywordYes6-digit NAICS, 4-digit SIC, 8-digit GICS code, or natural-language industry keyword.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: local execution with no API key and the size of each code universe (1,012 / 1,184 / 163). It stops short of describing what the mapping response contains or how ambiguity in keyword matching is handled.

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 tight sentences with the operational constraint (local, keyless) front-loaded before the capability statement. No filler, though the closing clause about 'SEC Review Office and applicable statutory suite recommendations' is dense jargon that could be plainer.

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

Completeness3/5

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

For a one-parameter lookup with rich annotations and no output schema, most of what an agent needs to invoke it is present. The gap is on the return side: 'bidirectionally with SEC Review Office and applicable statutory suite recommendations' does not tell the agent what fields come back or whether multiple matches can be returned for a keyword.

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 coverage is 100% for the single parameter, so the accepted formats are already documented in the schema. The description adds only the cardinality of each code set, which hints at the valid universe but not at format rules, normalization, or how a free-text keyword is resolved. Baseline 3 applies when the schema carries the semantics.

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?

Uses a specific verb ('Maps ... bidirectionally') against named resources (6-digit NAICS, 4-digit SIC, 8-digit GICS codes or industry keywords) and states the mapping target (SEC Review Office and statutory suite recommendations). An agent can tell this apart from siblings like get_live_us_statutory_rates_and_57_jurisdictions or execute_institutional_math_engine because it is a classification crosswalk, not a rates or math tool.

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?

Provides context that makes usage inferable ('runs locally with no API key required', 'bidirectionally', accepts keyword or code), which implicitly tells the agent this is the fallback when no credentialed lookup is wanted. However, it never states when to prefer or avoid this tool versus the statutory-rates or math-suite siblings, and gives no exclusions.

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