Skip to main content
Glama
Sign In

GISDB

by io.github.mooshee
OverviewDiscussionsAdmin

generate_veteran_packet

Read-onlyIdempotent

Return supplied-fact screening and a protected property-workspace handoff before application preparation. Despite the legacy tool name, this currently creates no documents, sends no email and files nothing. Select the saved property and review supporting evidence in the browser. No savings or qualification decision is returned.

Input Schema

NameRequiredDescriptionDefault
modeNoLegacy request label only. This tool returns screening gaps and a review handoff; it creates no documents and sends or files nothing.
addressNoLegacy alias for property_address; not a parcel lookup.
parcel_idNoExplicit county parcel or property account identifier.
state_codeNoReported two-letter state code; no default jurisdiction.
county_nameNoReported county. No county is inferred from an address.
review_yearNoRequested review year, separate from any county source or bill year.
veteran_nameNoApplicant name supplied for this review; never inferred from an account or VA record.
has_remarriedNoReported surviving-spouse remarriage status. Omit when unknown.
has_va_dic_awardNoReported VA survivor benefit award status. Omit when unknown.
property_addressNoExplicit property street address. Supply the parcel or account identifier separately.
rating_percentageNoLegacy alias for va_disability_percentage. Conflicting values remain unknown.
honorable_dischargeNoLegacy alias for is_honorable_discharge. Conflicting values remain unknown.
is_surviving_spouseNoWhether the applicant is a surviving spouse. This does not establish DIC, remarriage status or eligibility.
is_primary_residenceNoWhether this property is the applicant's primary residence for the requested review year. Omit when unknown.
is_honorable_dischargeNoReported honorable discharge status; no document verification is performed.
is_permanent_and_totalNoReported permanent-and-total status, separate from rating. Omit when unknown.
ownership_relationshipNoReported relationship to this property; does not establish ownership or delegated authority.
va_disability_percentageNoReported VA disability rating. A 100% rating alone does not establish permanent-and-total status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, but the description adds critical context beyond them: despite the name, no documents are created, no email is sent, nothing is filed, and no savings or qualification decision is returned. For a tool whose name implies document generation, this disclosure is exactly what an agent needs.

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?

Four tight sentences with the scope disclaimer front-loaded ahead of navigation advice. The language is slightly jargon-laden ('supplied-fact screening,' 'protected property-workspace handoff') but nothing is expendable.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description states what is and isn't returned (screening gaps, review handoff, no eligibility decision), which covers the main gap. With 18 well-documented parameters and read-only annotations, only the shape of the returned screening output remains unspecified.

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 18 parameters, including deprecated aliases and their conflict behavior, so the schema does the heavy lifting. The description adds no per-parameter guidance, 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?

The description names the two outputs (supplied-fact screening, protected property-workspace handoff) and explicitly disclaims the misleading legacy name by saying it creates no documents, sends no email, and files nothing. It is distinguishable from document-producing siblings such as generate_sf180_request, though the terms 'screening' and 'handoff' are somewhat abstract.

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?

It gives a light usage cue ('Select the saved property and review supporting evidence in the browser') but never states when to choose this over run_veteran_pilot_flow, check_veteran_relief, or audit_surviving_spouse_vet_relief. Usage is implied rather than explicitly routed.

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