Skip to main content
Glama

pulsenetwork

by com.theaslangroupllc.pulse

vetpulse

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.15): Veteran disability rating analysis (US, UK, Canada, Australia, NZ, Germany) • aid-attendance ($0.15): Veteran pension / Aid & Attendance-style eligibility (US, UK, Canada, Australia, NZ, Germany) • tdiu ($0.15): TDIU / unemployability eligibility (US, UK, Canada, Australia, NZ, Germany) • claim-builder ($0.20): Veteran disability claim evidence strategy (US, UK, Canada, Australia, NZ, Germany) • caregiver ($0.10): Veteran family caregiver stipend and benefits (US, UK, Canada, Australia, NZ, Germany) • education ($0.10): Veteran education benefit comparison (US GI Bill; UK, Canada, Australia, NZ, Germany equivalents) • state-benefits ($0.10): State/regional veteran benefits (US states; UK, Canada, Australia, NZ, Germany regions) • home-loan ($0.08): Veteran home-buying assistance analysis (US VA loan; Australia DHOAS; UK Forces Help to Buy) • discounts ($0.05): Verified veteran discounts by category (US, UK, Canada, Australia, NZ, Germany) • healthcare ($0.08): Veteran healthcare priority/coverage analysis (US, UK, Canada, Australia, NZ, Germany)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoVeteran age
langNoResponse language — any language supported
needsNoCare needs description (e.g. 'requires daily assistance with bathing, dressing, and medication management')
stateNoUS state/region (helps infer country if omitted)
actionYesWhich endpoint to call. Options: disability | aid-attendance | tdiu | claim-builder | caregiver | education | state-benefits | home-loan | discounts | healthcare
assetsNoTotal net worth in USD excluding primary home and one vehicle
branchNoMilitary branch — affects reserve component benefit calculations
incomeNoMonthly gross income in USD (Social Security, pension, other)
ratingNoCurrent combined disability rating (e.g. '70' or '60')
chapterNoGI Bill chapter of interest (e.g. '33', '30', '35', '1606') — or omit for full comparison
countryNoCountry whose veteran disability system to assess: US, UK, Canada, Australia, New Zealand, or Germany (other countries supported on a best-effort basis). Defaults to US if omitted and cannot be inferred.
categoryNoDiscount category. Defaults to all.
care_costNoMonthly unreimbursed care costs in USD — deducted from income for pension calculation
conditionNoVeteran's condition(s) requiring care
conditionsNoComma-separated medical conditions (e.g. 'tinnitus,PTSD,lumbar strain,sleep apnea')
dependentsNoWhether veteran has dependents — affects DEA transferability and some benefit calculations
service_eraNoService era for presumptive condition assessment (e.g. 'Vietnam', 'Gulf War', 'OEF', 'OIF', 'Korea')
work_historyNoWork history and current work status (e.g. 'cannot maintain substantially gainful employment due to PTSD and chronic pain')
prior_va_loanNoWhether veteran has used a VA loan before — triggers entitlement restoration guidance
current_ratingNoCurrent combined rating if filing a supplemental or new claim
priority_groupNoCurrent VA priority group if known (1–8)
purchase_priceNoTarget home purchase price in USD — used to calculate funding fee savings and PMI comparison
school_locationNoSchool city and state — used to estimate monthly housing allowance (E-5 with dependent BAH rate)
previous_denialsNoDescription of any previous claim denials — affects strategy (HLR vs. Board appeal vs. supplemental)
surviving_spouseNoSet true if applicant is a surviving spouse of a veteran — unlocks Survivors Pension and different Aid & Attendance rates
disability_ratingNoVA disability rating percentage — many state benefits require minimum rating (e.g. '70', '100', 'P&T')
caregiver_relationshipNoCaregiver's relationship to veteran (e.g. 'spouse')

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It reveals that output is AI-synthesized, lists coverage areas, and provides per-endpoint pricing. But it does not describe output format, error behavior, or any side effects, which is a moderate gap for an API with this many actions.

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 well-structured with a front-loaded summary followed by a clean bullet list of endpoints. It is somewhat long due to repeating coverage for each endpoint, but the organization makes it scannable and each item earns its place.

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?

For a complex tool with 27 parameters and 10 endpoints, the description provides a solid overview and endpoint breakdown. Since there is no output schema, it minimally hints at return values through endpoint descriptions, but lacks concrete examples or output format details, leaving some gaps.

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?

The schema already provides 100% coverage of parameter descriptions, so the description adds little semantic value beyond what is structured. The endpoint descriptions in the tool text duplicate the action enum details without enhancing understanding of individual parameters.

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 identifies VetPulse as a veterans benefits intelligence API, listing exactly what it does (AI-synthesized guidance on disability, pension, TDIU, etc.) and enumerating endpoints. This sharply distinguishes it from sibling 'pulse' tools that target 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 endpoint list gives clear context for what each action is used for, effectively telling the agent when to call which endpoint. However, it does not explicitly state when not to use this tool or mention alternative sibling tools, so it misses explicit exclusions.

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

All pulsenetwork toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation4/5

Each tool has a unique domain prefix (e.g., airdroppulse, alphapulse, arbipulse) making them mostly distinguishable at a glance. A few adjacent verticals like careerpulse vs talentpulse or marketpulse vs dealpulse have overlapping themes, but their descriptions clarify the distinct focus. The utility tools (catalog_search, discover, get_openapi_spec, x402_troubleshoot) are also clearly distinct in role. However, the sheer number of similar 'pulse' names could still cause misselection without reading descriptions.

Naming Consistency4/5

The dominant naming convention is `<domain>pulse` (e.g., climatepulse, cryptopulse, edupulse), which is highly consistent and predictable. Exceptions like catalog_search, discover, get_openapi_spec, x402_troubleshoot, and stateedge break the pattern, but these are few and serve obvious utility purposes. Overall, the convention is clear and easily learnable.

Tool Count2/5

With 80 tools, the server presents an extremely large and potentially overwhelming surface. While each tool represents a distinct intelligence vertical and navigation aids exist (catalog_search, discover, get_openapi_spec), the count far exceeds the typical 3-15 range for coherent agent use and even the 'heavy' 16-25 range. The burden of selecting the correct vertical from 80 options is significant, despite clear naming.

Completeness5/5

The server offers an exceptionally broad and deep coverage of domains, from finance and health to agriculture and gaming. Each vertical includes multiple endpoints that address core operations for its domain, such as search, analysis, comparisons, deterministic checks, and even action-oriented tools like letter generators and physical mail. The presence of free discovery and troubleshooting tools fills potential gaps, leaving no obvious dead ends in the overall tool surface.

Resources