GISDB

audit_va_funding_fee_refund

Read-onlyIdempotent

Audit eligibility and draft statutory lender demand letter for full refund of VA Home Loan Funding Fee under 38 U.S.C. § 3729(c) for veterans awarded retroactive service-connected disability ratings.

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>",
      "lender_name": "<lender_name>",
      "loan_amount": "<loan_amount>",
      "applied_funding_fee_percentage": "<applied_funding_fee_percentage>",
      "va_disability_percentage": "<va_disability_percentage>",
      "closing_date": "<closing_date>",
      "rating_effective_date": "<rating_effective_date>"
    },
    "name": "audit_va_funding_fee_refund"
  }
}

Input Schema

Name	Required	Description
`lender_name`	Yes	Originating or current mortgage lender name
`loan_amount`	Yes	Base loan amount before funding fee
`loan_number`	No	Mortgage loan number
`closing_date`	Yes	Mortgage loan closing date (YYYY-MM-DD)
`veteran_name`	Yes	Veteran's legal name
`rating_effective_date`	Yes	Effective date of service-connected rating from VA Rating Decision (YYYY-MM-DD)
`va_disability_percentage`	Yes	Current VA disability rating percentage (min 10%)
`applied_funding_fee_percentage`	Yes	VA funding fee percentage charged (e.g. 2.15)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. Description adds legal basis and output artifact (demand letter), but does not disclose audit criteria, return format, or limitations.

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?

Single front-loaded sentence with no redundant wording. Legal citation and eligibility condition included 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?

No output schema, 8 params fully described, annotations present. Description lacks detail on audit logic, what the letter contains, and eligibility determination, leaving gaps for a legal/financial tool.

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% and all 8 parameters are documented in the schema. Description adds no parameter meaning beyond schema; 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 specific actions 'Audit eligibility and draft statutory lender demand letter' and resource 'VA Home Loan Funding Fee' with legal citation. Clear but does not explicitly differentiate from sibling VA audit tools.

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?

Implies applicable population ('veterans awarded retroactive service-connected disability ratings') but gives no when-to-use vs alternatives, no prerequisites, 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 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.