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

Compute Live US .gov Rates & 57-Jurisdiction Tax Apportionment (Keyless Local)

get_live_us_statutory_rates_and_57_jurisdictions
Read-onlyIdempotent

Retrieve live NY Fed SOFR and EFFR benchmarks and compute apportioned combined federal and state effective corporate tax rates across all 57 US jurisdictions.

Instructions

Runs locally with no API key required. Pulls live NY Fed SOFR & EFFR + 24 official federal benchmarks and computes apportioned state + federal IRC Sec 11 combined effective corporate tax rates across all 57 US jurisdictions (50 States, DC, PR, GU, VI, AS, MP, US).

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

Input Schema

NameRequiredDescriptionDefault
sales_shareNoOptional in-state sales factor ratio (0.0 to 1.0, default 1.0).
jurisdictionNoOptional 2-letter US State, DC, PR, GU, VI, AS, MP, or US code.
payroll_shareNoOptional in-state payroll factor ratio (0.0 to 1.0, default 1.0).
property_shareNoOptional in-state property factor ratio (0.0 to 1.0, default 1.0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, open-world), so the bar is lower, and the description still adds real context: no API key or auth needed, a live outbound pull from NY Fed SOFR/EFFR plus 24 federal benchmarks. What it omits is latency/caching/failure behavior and whether 'live' means results shift between calls despite idempotentHint.

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 operator-relevant constraint (local, keyless) before the data sources and output scope. Dense but essentially every clause carries information; the parenthetical enumeration of territories is the only slightly bulky part.

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?

Without an output schema, the description should say what comes back (a single combined rate, or a per-jurisdiction table?) and whether passing 'jurisdiction' narrows the result or merely labels it — neither is stated. It is adequate for a keyless read-only computation but leaves these call-shaping questions open.

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%, so the four share/jurisdiction parameters are already documented, and the baseline of 3 applies. The description uses the word 'apportioned' but never explains how the sales/payroll/property factors are weighted or what happens when they are omitted, so it adds no meaning beyond the schema.

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 computation ('computes apportioned state + federal IRC Sec 11 combined effective corporate tax rates') over a specific scope (57 US jurisdictions, enumerated). An agent can tell this is the rate-computation tool and not the covenant/tariff or math-engine siblings. It does not explicitly name or exclude a sibling, which keeps it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no routing against the sibling tools (e.g., execute_institutional_math_engine). A reader must infer that this is the tool for statutory/apportioned tax rates purely from the resource named. The only usage-adjacent statement is the operational note about running locally without an API key.

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