Untax

generate_sf180_request

Idempotent

Generate official Standard Form SF-180 (Request Pertaining to Military Records) to retrieve military discharge Copy 4 (DD-214 Member-4) from the National Personnel Records Center (NPRC) in St. Louis for property tax relief.

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": "generate_sf180_request"
  }
}

Input Schema

Name	Required	Description
`ssn_last4`	No	Last 4 digits of SSN
`is_deceased`	No	Whether the veteran is deceased (for surviving spouse relief)
`veteran_name`	Yes	Full legal name used during military service
`date_of_entry`	No	Approximate date entered active service
`service_branch`	No	Branch of Armed Forces (e.g. 'U.S. Navy', 'U.S. Army')
`service_number`	No	Optional military service number or officer ID
`requester_address`	No	Return mailing address for NPRC delivery
`date_of_separation`	No	Approximate date of honorable discharge/separation
`requester_relationship`	No	Relationship to veteran (e.g. 'Self (Veteran)', 'Surviving Spouse')
`state_tax_relief_statute`	No	Target statutory authority (e.g. 'T.C.A. § 67-5-704')

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 the key traits: not read-only, idempotent, non-destructive, closed-world. The description adds useful domain context (which agency, which form copy, which purpose) but leaves a real ambiguity for a non-readOnly tool: whether it merely renders a fillable PDF or actually files the request with NPRC, and what side effect the agent should expect.

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 that packs the form identifier, its full official title, the exact record copy sought, the agency, and the downstream use case. Nothing is redundant and nothing could be cut without losing selection-relevant information.

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?

With 10 parameters and no output schema, the description should say what comes back (a completed PDF? a filing confirmation?) and any submission or signature requirements; it says none of that. It is complete enough for the agent to know when the tool is relevant, but not complete enough to predict its result.

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 10 parameters, so per-parameter meaning is fully documented in the schema itself. The description contributes no additional semantics such as format hints for dates, whether ssn_last4 is required in practice, or how requester_relationship interacts with is_deceased; 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 ('Generate') and a specific resource ('official Standard Form SF-180') and adds scope: DD-214 Copy 4 from NPRC for property tax relief. An agent knows exactly what artifact this produces, but the description never names a sibling or distinguishes itself from document-producing tools like generate_veteran_packet or generate_vso_referral.

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 purpose clause ('to retrieve military discharge Copy 4 ... for property tax relief') implies the situation in which to use it, but there is no explicit 'use this when' framing, no prerequisites (e.g. who must sign, whether the veteran must be the requester), and no mention of when a different tool would be preferred.

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

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