GISDB

audit_scra_interest_cap

Read-onlyIdempotent

Audit and enforce Servicemembers Civil Relief Act (50 U.S.C. § 3991) 6% delinquent property tax interest cap, strip unlawful county penalties, and issue stay of tax sale injunction.

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": {
      "servicemember_name": "<servicemember_name>",
      "active_duty_start_date": "<active_duty_start_date>"
    },
    "name": "audit_scra_interest_cap"
  }
}

Input Schema

Name	Required	Description
`parcel_id`	No	County parcel ID
`property_address`	No	Property street address
`branch_of_service`	No	Branch of Armed Forces (e.g. 'U.S. Army', 'USAF', 'USN', 'USMC')
`servicemember_name`	Yes	Active duty servicemember legal name
`active_duty_end_date`	No	Optional discharge date if service completed (YYYY-MM-DD)
`active_duty_start_date`	Yes	Start date of active duty service (YYYY-MM-DD)
`county_interest_rate_annual`	No	Annual interest rate charged by county (e.g. 0.18 for 18% or 0.12 for 12%)
`is_threatened_with_tax_sale`	No	True if county has scheduled a delinquent tax foreclosure auction
`billed_delinquent_tax_amount`	No	Base unpaid delinquent property taxes
`months_delinquent_during_service`	No	Number of months delinquency accrued during military service
`billed_accrued_interest_and_penalties`	No	Total accrued interest, penalties, and late charges billed by county

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

C2.9/5.0

Behavior1/5

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

The annotations declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, yet the description promises to 'enforce' the cap, 'strip unlawful county penalties,' and 'issue stay of tax sale injunction' — all plainly mutating actions against county records. This is a direct conflict that would badly mislead an agent deciding whether the call is safe or reversible.

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 three concrete clauses, no filler, and the statutory anchor placed early. Nothing could be cut without losing a distinct capability claim.

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?

For an 11-parameter tool with no output schema, the description never says what the audit produces — a recomputed interest figure, a refund amount, a filing, or all three. Combined with the unresolved read-versus-write ambiguity, an agent cannot predict the effect or result of invoking it.

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 11 parameters, including format hints (YYYY-MM-DD) and rate examples (0.18 for 18%), so the schema carries the parameter burden. The description adds no additional meaning about how inputs like months_delinquent_during_service or billed_accrued_interest_and_penalties are used in the computation.

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 set and resource: auditing and enforcing the SCRA 6% interest cap on delinquent property taxes, with a statutory citation (50 U.S.C. § 3991) that pins down the domain precisely. It does not, however, distinguish this from closely-named siblings like audit_property_tax, check_delinquent_taxes, or check_veteran_relief, so an agent cannot route between them on the description 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 legal trigger is implied (a servicemember's delinquent property tax bill exceeding the 6% cap), which is enough to recognize the situation. There is no explicit when-to-use statement, no prerequisites such as confirming active-duty overlap with the delinquency period, and no named alternative for related tax-audit work.

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

All GISDB tools Inspect

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.