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, which covers asking for a personal, buddy or lay statement, a statement in support, or a nexus letter the veteran already has to be rewritten, polished, tightened or cleaned up, 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. An id is the citation for a regulation or statute (38 CFR 14.636(b)), a short slug for a VA page or form (va-find-accredited-rep, va-form-21-526ez), and product-boundary for the one entry that states what VeteranHQ does and does not do, which carries no url because there is no document to open. A form is cited by its number, with its name in title. One kind of provenance is absent from sources and stays on the line as authority: the state veterans agency page, which is one state’s own contact page and changes with the state argument.

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 does not withhold it. A request that this tool act as the veteran's representative, attorney or agent before VA, 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; its kinds array lists every one of those classes the request crossed, in the precedence representation_request, words_for_testimony, review_lane_choice, preparation_request, and kind is the first of them. Ordinary requests for help are answered with no boundary object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / askedFor / description
      Previous value: -"What the veteran asked for, in their own words, when they are available. It changes nothing about the routing and never withholds it. A request that this tool act as the veteran's representative, attorney or agent before VA, 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; its kinds array lists every one of those classes the request crossed, in the precedence representation_request, words_for_testimony, review_lane_choice, preparation_request, and kind is the first of them. Ordinary requests for help are answered with no boundary object."New value: +"What the veteran asked for, in their own words, when they are available. It changes nothing about the routing and does not withhold it. A request that this tool act as the veteran's representative, attorney or agent before VA, 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; its kinds array lists every one of those classes the request crossed, in the precedence representation_request, words_for_testimony, review_lane_choice, preparation_request, and kind is the first of them. Ordinary requests for help are answered with no boundary object."
  2. Changed1 schema field changed
    • changedInput schema / properties / askedFor / description
      Previous value: -"What 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."New value: +"What the veteran asked for, in their own words, when they are available. It changes nothing about the routing and never withholds it. A request that this tool act as the veteran's representative, attorney or agent before VA, 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; its kinds array lists every one of those classes the request crossed, in the precedence representation_request, words_for_testimony, review_lane_choice, preparation_request, and kind is the first of them. Ordinary requests for help are answered with no boundary object."
  3. Added

TDQS

A4.2/5.0
Behavior5/5

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

Far exceeds the annotations (readOnly/idempotent/closed-world). It discloses determinism ('it reads no account data, so the answer is the same for every caller with the same inputs'), boundary-object behavior for out-of-scope requests with fixed precedence ordering, the null/false edge case for an unmatched state code, the provenance/sourceIds citation model, and the one authority that stays on the line rather than in sources. This is unusually rich behavioral disclosure beyond structured fields.

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

Conciseness3/5

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

The usage trigger is correctly front-loaded in the first sentence, but the rest is a single enormous run-on paragraph with repeated phrasing ('does not change the routing and does not withhold it' appears twice, echoing the schema). Much of the provenance/citation detail is justified by the absence of an output schema, but the lack of breaks or ordering makes the routing rules hard to extract.

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?

With no output schema, the description carries the full burden and does so: it explains the routeNow/message shape, the boundary object and its kinds precedence, sources with stable ids and sourceIds back-references, stateAgency/coverage.stateResolved edge cases, and the authority exception for state agency pages. An agent has enough to interpret both normal and boundary responses without a return schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: urgent controls ordering of routeNow without changing crisis routing; askedFor never changes or withholds routing but conditionally adds a boundary object whose kinds follow a fixed precedence; omitting state suppresses the state agency line, and an unmatched code yields stateAgency null with coverage.stateResolved false. This goes beyond the schema text, though much of it duplicates the parameter descriptions.

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 states a specific function: given a veteran's need, it returns accredited representation routes (VSOs, attorneys/claims agents), the VA OGC accreditation search, the VA.gov find-a-rep tool, state agency, phone numbers, documents and forms, and it handles crisis routing. It also draws explicit self-boundaries ('names no individual, firm or private directory', 'does not prepare, submit or file any form'), which separates it from adjacent tools like search_legal_authority. The core purpose is clear, though the dense enumeration of return payloads partially buries it.

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?

Opens with an explicit trigger: 'Use this when a veteran asks who can help them with a VA disability claim, or when they describe a crisis.' It also states a routing rule (crisis content only when need is crisis) and clarifies that urgent does not override crisis routing. What is missing is explicit naming of alternative siblings or when NOT to call this tool versus, e.g., search_legal_authority for the underlying regulations.

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