Skip to main content
Glama
Sign In

GISDB

by io.gisdb
OverviewDiscussionsAdmin

audit_veteran_sah_ada_exclusion

Read-onlyIdempotent

Audit eligibility and format Specially Adapted Housing (SAH) and ADA accessibility assessment exclusion under 38 U.S.C. § 2101 & T.C.A. § 67-5-601 to excise medically necessary mobility improvements from residential property assessment.

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>",
      "property_address": "<property_address>",
      "accessibility_improvements_cost": "<accessibility_improvements_cost>"
    },
    "name": "audit_veteran_sah_ada_exclusion"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcel_idYesCounty parcel ID / APN
county_nameNoCounty name
veteran_nameYesVeteran's legal name
county_tax_rateNoCombined county and municipal tax rate per $100 assessed (default 3.0137)
property_addressYesProperty street address
has_sah_or_sha_grantNoWhether veteran received VA Specially Adapted Housing or Special Home Adaptation grant (VA Form 26-4555)
va_disability_percentageNoVA service-connected disability percentage (min 10% or physician certified)
accessibility_improvements_costYesDocumented contractor/material cost of accessibility improvements (ramps, roll-in showers, lifts)
current_assessed_improvement_valueNoCurrent building assessed value on county CAMA card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 and determinism profile is covered. The description adds the substantive behavior — that it excises accessibility-improvement value from the assessed improvement amount — but does not say how the exclusion is computed or what it returns. With annotations carrying the operational profile, a 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with the action verb first, which is good structure, but it is dense with statutory citations and stacked acronyms (SAH, ADA, SH A implied) that consume space without clarifying agent behavior. Some of that legal framing could be trimmed without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 indicates what the audit returns — an eligibility boolean, a dollar exclusion amount, or a formatted filing packet — which matters for a 9-parameter tool whose name says it 'formats' something. Eligibility thresholds, failure conditions when the veteran lacks a grant, and the relationship to sibling veteran audits are also unaddressed.

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?

All 9 parameters have schema descriptions at 100% coverage, including the default tax rate and the VA Form 26-4555 reference, so the schema does the heavy lifting. The description adds no per-parameter meaning beyond restating the domain; baseline 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?

Uses a specific verb ('Audit eligibility and format') on a specific resource ('Specially Adapted Housing (SAH) and ADA accessibility assessment exclusion') and anchors it in named statutes (38 U.S.C. § 2101, T.C.A. § 67-5-601). An agent can tell this concerns excising mobility-improvement value from a residential assessment, but nothing in the text distinguishes it from near siblings such as audit_disabled_veteran_relief or audit_property_tax.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no prerequisites (e.g., that a VA grant or physician certification is needed), and no named alternative for the neighboring veteran-relief audits. Usage is only inferable from the statutory citations and the 'medically necessary mobility improvements' phrase.

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

All GISDB toolsInspect
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.

Resources