Skip to main content
Glama

vetpulse

Analyze VA disability, pension, and education benefits eligibility with AI-synthesized guidance. Get claim strategies, caregiver stipends, and state-specific benefits for US veterans.

Instructions

VetPulse: US veterans benefits intelligence API. AI-synthesized guidance on VA disability compensation, Aid & Attendance pension, TDIU, claim strategy, caregiver stipends, GI Bill, state benefits, VA healthcare

Coverage: Global

Endpoints: • disability ($0.10): VA disability rating analysis • aid-attendance ($0.10): VA Aid & Attendance pension eligibility • tdiu ($0.10): TDIU (Total Disability Individual Unemployability) eligibility • claim-builder ($0.10): VA disability claim evidence strategy • caregiver ($0.10): PCAFC caregiver stipend and benefits • education ($0.10): GI Bill and education benefit comparison • state-benefits ($0.10): State-specific veteran benefits (all 50 states) • home-loan ($0.10): VA home loan benefit analysis • discounts ($0.10): Verified veteran discounts by category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: disability | aid-attendance | tdiu | claim-builder | caregiver | education | state-benefits | home-loan | discounts
langNoResponse language — any language supported
conditionsNoComma-separated medical conditions (e.g. 'tinnitus,PTSD,lumbar strain,sleep apnea')
service_eraNoService era for presumptive condition assessment (e.g. 'Vietnam', 'Gulf War', 'OEF', 'OIF', 'Korea')
ageNoVeteran age
needsNoCare needs description (e.g. 'requires daily assistance with bathing, dressing, and medication management')
incomeNoMonthly gross income in USD (Social Security, pension, other)
assetsNoTotal net worth in USD excluding primary home and one vehicle
care_costNoMonthly unreimbursed care costs in USD — deducted from income for pension calculation
surviving_spouseNoSet true if applicant is a surviving spouse of a veteran — unlocks Survivors Pension and different Aid & Attendance rates
ratingNoCurrent combined disability rating (e.g. '70' or '60')
work_historyNoWork history and current work status (e.g. 'cannot maintain substantially gainful employment due to PTSD and chronic pain')
current_ratingNoCurrent combined rating if filing a supplemental or new claim
previous_denialsNoDescription of any previous claim denials — affects strategy (HLR vs. Board appeal vs. supplemental)
relationshipNoCaregiver relationship to veteran (e.g. 'spouse', 'adult child', 'parent', 'sibling')
veteran_needsNoDescription of veteran's care needs (e.g. 'severe TBI requires 24hr supervision, cannot be left alone')
discharge_dateNoApproximate discharge date — PCAFC eligibility expanded in 2020 to all service eras
chapterNoGI Bill chapter of interest (e.g. '33', '30', '35', '1606') — or omit for full comparison
branchNoMilitary branch — affects reserve component benefit calculations
school_locationNoSchool city and state — used to estimate monthly housing allowance (E-5 with dependent BAH rate)
dependentsNoWhether veteran has dependents — affects DEA transferability and some benefit calculations
stateNoUS state name or abbreviation (e.g. 'Texas', 'TX')
disability_ratingNoVA disability rating percentage — many state benefits require minimum rating (e.g. '70', '100', 'P&T')
purchase_priceNoTarget home purchase price in USD — used to calculate funding fee savings and PMI comparison
prior_va_loanNoWhether veteran has used a VA loan before — triggers entitlement restoration guidance
categoryNoDiscount category. Defaults to all.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the tool is 'AI-synthesized guidance', lists endpoint costs, and describes parameters. It does not detail response format or limitations, but coverage and pricing are transparent.

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?

The description is structured with a clear heading, coverage statement, and bulleted endpoints. It is somewhat long but each section adds value given the number of endpoints and parameters.

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?

With 26 parameters, no output schema, and no annotations, the description effectively explains the tool's purpose, endpoints, and parameter usage. It lacks return format details but is reasonably complete for an intelligence API.

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 description coverage is 100% with detailed parameter descriptions. The tool description adds value by listing endpoints with pricing and providing an overview of the tool's purpose, which is not captured in the schema.

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 clearly states it is a 'US veterans benefits intelligence API' and lists specific endpoints like disability, aid-attendance, TDIU, etc., distinguishing it from sibling tools that cover other domains.

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 explicit endpoint names and their purposes, guiding users on when to use each sub-action. It does not explicitly state when not to use the tool or compare to siblings, but the endpoint list offers clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server