Untax

audit_disabled_homeowner_relief

Read-onlyIdempotent

Screen eligibility for Tennessee Disabled Homeowner Property Tax Relief under T.C.A. § 67-5-703. Calculates exact tax relief on up to $30,000 market value cap ($7,500 assessed) for totally disabled homeowners with household income under $33,460.

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": {
      "homeowner_name": "<homeowner_name>",
      "annual_income": "<annual_income>",
      "has_ssdi_or_ssi_award": "<has_ssdi_or_ssi_award>"
    },
    "name": "audit_disabled_homeowner_relief"
  }
}

Input Schema

Name	Required	Description
`parcel_id`	No	Parcel ID
`market_value`	No	Total appraised market value of property
`annual_income`	Yes	Total household annual income (must be <= $33,460)
`homeowner_name`	Yes	Homeowner legal name
`property_address`	No	Property street address
`is_primary_residence`	No	Whether property is owned and occupied as primary residence on Jan 1
`has_ssdi_or_ssi_award`	Yes	Whether homeowner has SSA/SSDI permanent total disability determination

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered; the description adds real domain context beyond that: the $30,000 market value cap, the $7,500 assessed figure, and the $33,460 income ceiling. It stops short of describing what is returned for an ineligible homeowner or how partial eligibility is reported.

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?

Two dense sentences with the program scope front-loaded and the calculation parameters second. No filler, no restatement of the tool name, and every clause carries substantive information.

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?

There is no output schema, yet the description never says what the response contains — an eligibility verdict, a computed relief dollar amount, or both — nor how an ineligible or partially documented applicant is handled. With seven parameters and a statutory calculation, more of the result shape should be disclosed.

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 100%, so the schema documents all seven fields and the baseline would be 3. The description adds meaning beyond it by tying annual_income and market_value to concrete statutory thresholds, telling the agent what values actually matter for screening.

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?

Names a specific verb and resource ('Screen eligibility for Tennessee Disabled Homeowner Property Tax Relief') plus the governing statute, and states the second function ('Calculates exact tax relief'). This clearly separates it from siblings like audit_disabled_veteran_relief or audit_senior_tax_freeze.

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?

The statutory scope and eligibility criteria imply when the tool applies, but there is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for adjacent relief programs. An agent must infer routing from the program name alone.

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

All Untax tools Inspect

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.