Skip to main content
Glama

audit_senior_tax_freeze

Read-onlyIdempotent

Audit eligibility and calculate projected 5-year savings for the Tennessee Senior Property Tax Freeze under T.C.A. § 67-5-705 (Constitutional Amendment 2) locking tax obligations at base year.

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": {
      "owner_name": "<owner_name>",
      "owner_age": "<owner_age>",
      "annual_household_income": "<annual_household_income>",
      "current_year_tax_bill": "<current_year_tax_bill>"
    },
    "name": "audit_senior_tax_freeze"
  }
}

Input Schema

NameRequiredDescriptionDefault
owner_ageYesAge of owner as of December 31
parcel_idNoParcel ID
owner_nameYesProperty owner name
county_nameNoCounty name
property_addressNoProperty street address
current_year_tax_billYesCurrent year total property tax bill
annual_household_incomeYesAnnual household income (ceiling: $45,000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds the legal basis and states that it audits eligibility and projects five-year savings, but it does not describe return structure, ineligibility behavior, calculation assumptions, or data sources. It adds some value beyond annotations but leaves meaningful operational detail unspecified.

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?

A single, front-loaded sentence naming the action, program, statute, and mechanism. Every clause adds legal or program specificity and there is no filler.

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 specialized audit and calculation tool with no output schema, the definition gives the program and statute but omits eligibility thresholds beyond income, calculation assumptions, and expected return shape. It is adequate for selecting the tool, but less complete for understanding or interpreting its results.

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% and all seven parameters are self-documented, including the income ceiling. The description adds no parameter-level semantics beyond the broader program context and base-year locking, so the baseline of 3 applies.

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?

States a specific verb ('Audit eligibility and calculate projected 5-year savings'), resource ('Tennessee Senior Property Tax Freeze'), statute, and mechanism ('locking tax obligations at base year'). The program specificity distinguishes it from sibling relief audits even without naming them.

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?

Implied usage is clear when a user asks about Tennessee senior property tax freeze eligibility or savings. However, there is no explicit when-to-use guidance versus alternatives, no exclusions, and no prerequisites beyond what the schema provides; the agent must infer boundaries from the program name.

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.