Skip to main content
Glama

Find free and accredited claim help

find_claim_help
Read-onlyIdempotent

Use this when a veteran asks who can help them with a VA disability claim, or when they describe a crisis. The Veterans Crisis Line comes first, in full, when need is crisis, and no other need returns crisis content. Setting urgent true puts the veteran’s first action at the top of routeNow and does not change the crisis routing. Every result carries accredited representation routes: VA accredited Veterans Service Organizations, whose services on VA benefit claims are free, and accredited attorneys and claims agents, who may charge fees only for representation provided after VA issues notice of an initial decision on the claim (38 CFR 14.636(c) and 38 U.S.C. 5904(c)(1)). It also returns the VA Office of General Counsel accreditation search and the VA.gov find a representative tool, the state or territory veterans agency matching a two-letter state code, VA phone numbers suited to the need, the documents worth bringing, and links to the VA forms that need points at. It names no individual, firm or private directory. It does not prepare, submit or file any form, and it reads no account data, so the answer is the same for every caller with the same inputs. A two-letter code with no agency on file returns stateAgency null and coverage.stateResolved false, with the national routes unchanged. The askedFor argument carries the veteran’s own words. It does not change the routing and does not withhold it: a request that this tool or the model calling it act as the veteran’s attorney, agent or representative before VA, a request to supply words for a veteran or a clinician to use, to choose a decision review lane for the veteran, or to prepare or file a claim returns status ok with the same findings, plus a boundary object whose kind names the primary boundary crossed and whose kinds lists every boundary the request crossed, in the fixed precedence representation_request, then words_for_testimony, then review_lane_choice, then preparation_request, so a request that crosses two keeps both. Its opening, rule and route state what VeteranHQ does not do, one sentence per kind in kinds, the accreditation rule (38 CFR 14.629) and the fee rule (38 CFR 14.636, 38 U.S.C. 5904(c)(1)), and where the work belongs; those instruments are merged into sources and the same paragraph leads message, behind the Veterans Crisis Line when need is crisis. Provenance is indexed rather than repeated: sources is the registry of full references, each with a stable id, and every guidance line and the boundary carry sourceIds into it. A line’s citation is the sources entry whose id it names, and its passage is line.quote when that field is present and that entry’s quote otherwise. Two kinds of provenance are absent from sources and stay on the line as authority: the state veterans agency page and the VeteranHQ product boundary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needYesWhat the veteran is trying to do. Use general when the veteran has not said, and crisis when they describe a mental health emergency.
stateNoTwo-letter US state or territory code, for example CA, TX or PR. Adds that state veterans agency to the answer. Omit it when the veteran has not said where they live.
urgentNoTrue when the request is time sensitive, for example a letter, an exam notice or a date the veteran is worried about. It puts their first action at the top of the answer. It does NOT change the crisis routing: use need crisis when the veteran describes a mental health emergency.
askedForNoWhat the veteran asked for, in their own words, when they are available. It changes nothing about the routing and never withholds it. A request to prepare or file a claim, to choose a decision review lane for the veteran, or to supply words for a veteran or a clinician to use returns the same answer with a boundary object added, naming what VeteranHQ does not do, the accreditation and fee rules and where the work belongs; ordinary requests for help are answered with no boundary object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining that it 'reads no account data' and that the answer is the same for every caller with the same inputs, explicitly addresses crisis routing behavior, and details the boundary object and provenance system. It also describes legal/fee restrictions. Nothing in the description contradicts the readOnlyHint or idempotentHint annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single long paragraph with dense legal, routing, and provenance details that are not essential for an agent to select or invoke the tool. The first sentence is an excellent front-loaded hook, but the rest is a wall of text that would be better split into 'When to use', 'What it returns', 'Edge cases', and 'Provenance' sections. Its sheer length hurts scanability.

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

Completeness5/5

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

Given the tool has 4 parameters, no output schema, and a complex routing/urgency/crisis behavior, the description covers all edge cases: invalid state code, crisis routing precedence, urgent flag, askedFor restrictions, return contents, and limits. It is comprehensive enough for an agent to understand the tool's behavior and response structure without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema descriptions are already thorough, but the description adds additional meaning: it clarifies that `urgent` only changes the order of the first action, not the crisis routing; it details the edge case behavior of `state` (null when no agency on file); and it explains that `askedFor` triggers the boundary object for prohibited requests. These additions go beyond the schema and give the agent essential nuances.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with an explicit use case: 'Use this when a veteran asks who can help them with a VA disability claim, or when they describe a crisis.' This names the specific verb (find/help) and resource (claim help) and clearly distinguishes the tool from sibling tools that analyze ratings or calculate compensation. The boundary behavior further reinforces what the tool does and does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool, including the crisis route that is separate from urgent routing: 'Setting urgent true ... does not change the crisis routing.' It also implicitly excludes its use for non-help tasks by stating 'It does not prepare, submit or file any form.' However, it never names an alternative sibling tool or explicitly says 'use tool X instead' for other scenarios.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources