Skip to main content
Glama
Sign In

Untax

by io.untax
OverviewDiscussionsAdmin

verify_va_disability_exemption

Read-onlyIdempotent

Verify federal VA disability rating (100% P&T, TDIU, SAH) under 38 U.S.C. Chapter 11 and map directly to state/county property tax exemption caps and vouchers.

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>"
    },
    "name": "verify_va_disability_exemption"
  }
}

Input Schema

NameRequiredDescriptionDefault
state_codeNoTarget state ('TN', 'GA', etc.)
county_nameNoTarget county name
veteran_nameYesVeteran legal name
service_branchNoService branch (e.g. 'U.S. Army', 'USAF', 'USMC')
effective_tax_rateNoEffective tax rate
parcel_market_valueNoAppraised market value of primary residence
is_permanent_and_totalNoTrue if rating decision grants Permanent & Total (P&T)
combined_rating_percentNoCombined VA disability rating percentage (0 to 100)
has_individual_unemployability_tdiuNoTrue if veteran receives Total Disability based on Individual Unemployability
has_specially_adapted_housing_grantNoTrue if veteran received 38 U.S.C. § 2101 SAH grant

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, idempotentHint, closed-world, and non-destructive behavior, so the description does not need to restate safety. It adds the legal basis (38 U.S.C. Chapter 11) and the output focus (exemption caps and vouchers), but does not disclose what 'verify' means operationally or what determination is returned.

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 with no filler. It states the federal verification target and the state/county mapping outcome efficiently.

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 10-parameter tool with no output schema, the description is thin on what the verification returns and how state/county caps are selected when location parameters are omitted. Annotations cover the safety profile and the schema covers parameters, but the output behavior remains under-described.

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 every parameter including veteran_name, rating percentages, TDIU, P&T, and SAH is already documented. The description's mention of 100% P&T, TDIU, and SAH adds conceptual mapping but no parameter-specific syntax or constraints beyond the schema.

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 ('Verify') and resource ('federal VA disability rating') and adds the mapping to state/county property tax exemption caps and vouchers, which distinguishes it from pure rating parsers. It does not explicitly name a sibling or state when to prefer another tool, so it falls short of a 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 implied by the description: verify a veteran's federal rating and map it to local exemption caps. There is no explicit when-to-use versus alternatives, no prerequisites such as needing a rating decision document, and no exclusions.

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

All Untax 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