Skip to main content
Glama

audit_surviving_spouse_vet_relief

Read-onlyIdempotent

Audit eligibility and generate Form F-16 property tax relief application for unremarried surviving spouses of 100% P&T disabled veterans or service members killed in action under T.C.A. § 67-5-704(b).

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": {
      "surviving_spouse_name": "<surviving_spouse_name>",
      "deceased_veteran_name": "<deceased_veteran_name>",
      "is_unremarried": "<is_unremarried>",
      "is_primary_residence": "<is_primary_residence>"
    },
    "name": "audit_surviving_spouse_vet_relief"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcel_idNoParcel ID
market_valueNoCurrent total appraised market value
is_unremarriedYesTrue if surviving spouse has not remarried
military_branchNoBranch of Armed Forces
property_addressNoProperty street address
is_primary_residenceYesTrue if owned and occupied as primary residence on January 1
deceased_veteran_nameYesDeceased veteran legal name
surviving_spouse_nameYesSurviving spouse legal name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds the statutory basis (T.C.A. § 67-5-704(b)) and the qualifying conditions, which is real value. However, 'generate ... application' sits in mild tension with readOnlyHint and the description never clarifies that nothing is filed or submitted — an agent could reasonably wonder whether this produces a document or performs a submission.

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 dense sentence that front-loads the action and immediately narrows to the qualifying population and statute. No filler, no restatement of the title, nothing that could be cut without losing 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, so the description carries the burden of explaining what comes back; naming 'Form F-16 property tax relief application' partially does that, but the return format and the behavior when eligibility fails (e.g., does it still emit a form, or report ineligibility?) are unstated. For an 8-parameter, statutorily-gated audit-and-generate tool, this leaves a meaningful gap.

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 coverage is 100%, so all 8 parameters are already documented in the schema and baseline is 3. The description does add meaning by naming the eligibility gates (unremarried status, 100% P&T or KIA veteran status) that determine which required booleans matter, but it gives no syntax, format, or conditional-requirement detail beyond that.

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?

Specific verb pair ('audit eligibility', 'generate Form F-16') plus a precisely scoped beneficiary class ('unremarried surviving spouses of 100% P&T disabled veterans or service members killed in action') and a statutory citation. An agent knows exactly what the tool produces. It loses a point because it never distinguishes itself from close siblings like audit_surviving_spouse_portability or audit_disabled_veteran_relief, which an agent must disambiguate by name alone.

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 eligibility population is stated, which implicitly tells the agent when the tool applies, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for the adjacent surviving-spouse or disabled-veteran relief tools. The agent must infer routing from the beneficiary description rather than being told.

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.