Skip to main content
Glama

audit_veteran_living_trust_preservation

Read-onlyIdempotent

Audit and format Sworn Affidavit of Continued Beneficial Homestead Occupancy to preserve 100% disabled veteran statutory property tax relief after deeding residence to a revocable living trust under T.C.A. § 67-5-704(g) and Tex. Tax Code § 11.13(j).

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>",
      "trust_name": "<trust_name>",
      "veteran_is_primary_beneficiary": "<veteran_is_primary_beneficiary>",
      "has_lifetime_occupancy_right": "<has_lifetime_occupancy_right>"
    },
    "name": "audit_veteran_living_trust_preservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcel_idYesCounty parcel ID / APN
trust_nameYesFull legal name of revocable living trust
county_nameNoCounty name
veteran_nameYesVeteran's legal name
property_addressNoProperty street address
deed_recording_dateNoDate deed to trust was recorded with County Register of Deeds (YYYY-MM-DD)
has_lifetime_occupancy_rightYesWhether trust instrument explicitly grants lifetime right of residential occupancy
annual_property_tax_relief_usdNoAnnual statutory property tax relief amount to be preserved
veteran_is_primary_beneficiaryYesWhether veteran is the settlor/grantor and primary lifetime beneficiary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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, and openWorldHint=false, so the safety profile is largely covered. The description adds useful legal context (which statutory relief is being preserved and why the trust transfer endangers it), but it does not say what happens when has_lifetime_occupancy_right or veteran_is_primary_beneficiary is false, nor whether a failed audit still emits a document. With annotations carrying the safety burden, 3 is appropriate.

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 dense sentence with the action, the artifact, and the statutory basis front-loaded, with no filler. It is jargon-heavy (two long statutory citations) but every clause carries information. Slight readability cost from cramming purpose and legal justification together, but no wasted wording.

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 9-parameter, 5-required tool with no output schema, the description explains the legal purpose well but not the outcome: it never states whether the result is a formatted affidavit document, an eligibility verdict, or both, nor what the agent should do when a required attestation fails. Inputs are fully covered by the schema, so the remaining gap is the output/behavior side.

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 9 parameters, so every field is already documented in the schema. The description contributes no additional parameter meaning — it never mentions, for example, that deed_recording_date drives a statutory deadline or how annual_property_tax_relief_usd is used. Baseline 3 applies when the schema does the heavy lifting.

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 verb pair ('Audit and format') and a highly specific resource ('Sworn Affidavit of Continued Beneficial Homestead Occupancy'), plus the exact scenario (deeding a residence into a revocable living trust). That scenario detail is what separates it from generic siblings like audit_disabled_veteran_relief or check_veteran_relief. It stops short of explicitly naming a contrasting sibling, so it lands at 4 rather than 5.

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?

Usage is only implied: the agent can infer this applies after a residence has been deeded to a revocable living trust and relief is at risk under the cited statutes. There is no explicit 'use this when X, use sibling Y otherwise' routing, and no stated prerequisite such as having the trust instrument or recorded deed in hand. Adequate but with clear gaps for a 30-sibling catalog where confusion is likely.

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.