Skip to main content
Glama

bva-corpus

by com.veterans-rights

Check presumptive conditions

check_presumptive_conditions
Read-onlyIdempotent

Check whether a condition may be a PRESUMPTIVE service connection for a veteran — meaning VA presumes it is service-connected for qualifying service/exposure, so no medical nexus needs to be proven. Covers Agent Orange/herbicides, PACT Act burn pits & airborne hazards, Camp Lejeune water, ionizing radiation, and Gulf War illness. Returns who qualifies, the legal basis, representative conditions, and how many vetted BVA decisions granted on this basis. Lists are representative, not exhaustive; educational only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conditionNoClaimed condition, e.g. "type 2 diabetes", "asthma".
exposure_basisNoKnown/suspected exposure, if any.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesTool-specific result payload.
linkYesTagged deep link into the matching veterans-rights.com page.
disclaimerYesStanding not-legal-advice / not-VA framing.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint; the description adds meaningful context about being educational, that lists are representative, and what return information includes, exceeding annotation coverage.

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

Conciseness5/5

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

The description is a single paragraph of four sentences, front-loaded with main purpose, no waste, each sentence adds value.

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 schema, annotations, output schema, and sibling tools, the description fully covers the tool's behavior, limitations, and usage context.

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?

Schema description coverage is 100%, so the parameter descriptions are already clear. The tool description doesn't add significant new meaning beyond the schema's parameter descriptions.

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 the tool checks if a condition is a presumptive service connection, specifies covered exposure categories, and distinguishes it from sibling tools like list_conditions or search_bva_decisions.

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 explains when to use the tool (for presumptive conditions) and covers the scope, but does not explicitly state when not to use or name specific alternatives, though siblings imply context.

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

All bva-corpus 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

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose covering different aspects of VA disability claims and appeals, such as conditions, ratings, representatives, and decisions. There is no overlap that would cause confusion for an agent.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with descriptive verbs (check, estimate, explain, find, get, list, search) and snake_case naming. The pattern is predictable throughout the set.

Tool Count5/5

With 10 tools, the server is well-scoped for its educational purpose on veterans' benefits. Each tool provides essential functionality without excess or deficiency.

Completeness4/5

The tool set covers the main lifecycle of a VA claim: conditions, ratings, process, appeals, representatives, and decision search. Minor gaps exist (e.g., no tool for specific deadlines or filing), but core user needs are addressed.

Resources