Skip to main content
Glama

audit_retroactive_tax_recovery

Read-onlyIdempotent

Audit eligibility and format County Trustee demand voucher for retroactive property tax refunds under T.C.A. § 67-5-509 and state reciprocal rules when a veteran receives a retroactive VA effective date.

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": {
      "veteran_name": "<veteran_name>",
      "parcel_id": "<parcel_id>",
      "va_effective_date": "<va_effective_date>",
      "annual_tax_paid_usd": "<annual_tax_paid_usd>",
      "tax_years_pending": "<tax_years_pending>"
    },
    "name": "audit_retroactive_tax_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcel_idYesCounty parcel ID / APN
state_codeNoState code (e.g. 'TN')
county_nameNoCounty name
veteran_nameYesVeteran's legal name
property_addressNoProperty street address
tax_years_pendingYesPrior tax years eligible for refund (e.g. [2024, 2025])
va_effective_dateYesRetroactive effective date from VA Rating Decision (YYYY-MM-DD)
annual_tax_paid_usdYesAnnual real property tax paid
is_permanent_and_totalNoWhether disability is Permanent & Total
va_disability_percentageNoVA disability percentage (100% P&T)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, destructiveHint=false, so the safety profile is covered. The description adds that the tool both evaluates eligibility and emits a formatted voucher under a named statute, which the annotations cannot convey, but it is silent on what happens when eligibility fails, whether the voucher is returned as text or file, and any jurisdiction limits implied by 'state reciprocal rules'.

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 that front-loads the action and keeps the legal citation and trigger at the end. Dense legal phrasing but no filler or redundancy; it could be marginally more scannable if the trigger condition were broken out.

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 10-parameter tool with no output schema, the description covers purpose and legal basis but leaves the return value undefined — an agent cannot tell whether it receives a voucher document, an eligibility verdict, a computed refund amount, or a mix. Given annotations handle safety, the main remaining gap is output shape and ineligibility behavior.

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% across all 10 parameters, so the schema already documents each field including va_effective_date and tax_years_pending. The description adds conceptual framing (retroactive effective date drives eligibility) but no syntax, formats, or constraints beyond the schema — the baseline of 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?

States a specific compound action (audit eligibility + format a County Trustee demand voucher) on a specific resource (retroactive property tax refunds), gated on a concrete trigger (retroactive VA effective date). This separates it from broad siblings like audit_property_tax or lookup_property_tax, though it never names the closest alternative (audit_disabled_veteran_relief) explicitly.

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?

The clause 'when a veteran receives a retroactive VA effective date' is a genuine selection condition that tells the agent the triggering scenario. It stops short of exclusions or naming alternatives for the overlapping veteran-relief tools, so routing between audit_disabled_veteran_relief and this tool still requires inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.