Skip to main content
Glama

audit_disabled_veteran_wheel_tax

Read-onlyIdempotent

Audit eligibility and format County Disabled Veteran Motor Vehicle Registration and Wheel Tax Exemption Voucher under T.C.A. § 55-4-237 to exempt vehicle registration fees and county wheel taxes for qualifying disabled veterans.

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>",
      "county_name": "<county_name>",
      "vehicle_vin": "<vehicle_vin>",
      "va_disability_percentage": "<va_disability_percentage>"
    },
    "name": "audit_disabled_veteran_wheel_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
county_nameYesCounty name (e.g. 'Hamilton County')
vehicle_vinYesVehicle 17-character VIN
veteran_nameYesVeteran's legal name
is_permanent_and_totalNoWhether disability is certified Permanent & Total (P&T)
vehicle_make_model_yearNoVehicle year, make, and model (e.g. '2023 Ford F-150')
va_disability_percentageYesVA service-connected disability percentage (100% P&T or mobility impaired)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read (readOnlyHint=true, destructiveHint=false, idempotentHint=true), so the safety profile is covered. The description adds that it both audits eligibility AND formats a voucher document, which is useful behavioral context, but it does not say what happens when the veteran fails eligibility, what the voucher output looks like, or whether any fees/filings follow. With no output schema, that gap matters.

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 front-loaded sentence that leads with the action and resource before the statute citation, with no filler. It is dense but not padded; slightly long clause stacking is the only cost.

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 read-only tool with fully documented parameters and no output schema, the description covers the 'what' but omits the outcome shape of the generated voucher and the eligibility thresholds that determine success. An agent knows what to pass in but not what it will get back.

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%, so all six parameters (including the P&T flag and VA percentage) are already documented in the schema. The description adds no parameter-level meaning beyond what is there, so the 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?

States a specific verb (Audit) and concrete resource (County Disabled Veteran Motor Vehicle Registration and Wheel Tax Exemption Voucher) with a statute citation, so the scope is unmistakable. It does not distinguish itself from close siblings like audit_disabled_veteran_relief or audit_veteran_shield, leaving the agent to infer the boundary from the tool 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 Guidelines2/5

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

The phrase 'for qualifying disabled veterans' hints at eligibility gating but never states the qualifying conditions, prerequisites, or when this should be chosen over the veteran-relief siblings. There are no exclusions or alternative-tool routing, so usage must be inferred from the purpose sentence.

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.