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 with a VA disability claim, or describes a crisis. VeteranHQ does not prepare or file claims or forms, and only VA decides a claim. need crisis puts the full Veterans Crisis Line first and alone returns crisis content; urgent true tops routeNow with the first action, crisis routing unchanged. Results list accredited Veterans Service Organizations (free), attorneys and claims agents (fees only for representation provided after VA’s notice of an initial decision, 38 CFR 14.636(c), 38 U.S.C. 5904(c)(1)), VA’s accreditation search and representative finder, VA phone numbers, documents to bring, form links, and the veterans agency for a two-letter state code (none on file: stateAgency null, coverage.stateResolved false). It names no individual, firm or private directory and reads no account data. askedFor (the veteran’s words) does not change or withhold the routing: a request to act as the veteran’s attorney, agent or representative before VA, to supply words for a veteran or a clinician to use (statements or nexus letters, new, 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, the same findings and a boundary. Its kind names the primary boundary crossed; kinds lists every boundary the request crossed, in the fixed precedence representation_request, then words_for_testimony, then review_lane_choice, then preparation_request. Its opening, rule and route state, one sentence per kind in kinds, what VeteranHQ does not do, the accreditation and fee rules and where the work belongs, and lead message after any crisis line. sources holds each reference once by stable id (citation, VA page or form slug, or product-boundary, no url), cited by sourceIds; a line’s passage is line.quote or its entry’s quote; state agency pages stay on the line.

Input 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.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantial extra behavior: no claim preparation/filing, only VA decides, no individual/firm/directory names, no account data read, and the boundary-object mechanics of askedFor. This far exceeds what the annotations disclose.

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?

It is front-loaded with the trigger, which helps, but the body is a dense wall of run-on clauses mixing return-shape internals (sources, sourceIds, line.quote) with boundary logic. The length is far beyond what is needed and is hard to parse, so structure and economy are poor despite the strong lead.

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 return-shape burden and does so thoroughly: what results list, how crisis content is ordered, how the boundary object and kinds are populated, and how sources are deduplicated. For a complex routing tool, an agent has enough to call it correctly.

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 meaningfully adds interaction semantics beyond the schema: urgent tops routeNow while crisis routing is unchanged, askedFor never alters or withholds routing, and state with no agency on file yields stateAgency null and coverage.stateResolved false. It also defines the boundary kinds and their fixed precedence.

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 opening clause states a specific trigger and resource: match a veteran asking who can help with a VA disability claim, or in crisis, to accredited help. It is clearly distinguishable from siblings like find_veteran_benefits or search_legal_authority, though the actual verb ('find/surface accredited representatives and resources') is never stated as plainly as the routing behavior.

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?

Explicit triggers are given ('Use this when a veteran asks who can help... or describes a crisis'), plus precise conditions for urgent (time-sensitive, does NOT change crisis routing) and crisis (mental health emergency). It stops short of naming sibling alternatives to prefer under other conditions, so it is strong context without full alternative routing.

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