Skip to main content
Glama

bva-corpus

by com.veterans-rights

List conditions

list_conditions
Read-onlyIdempotent

List the standardized conditions the Veterans’ Rights corpus organizes Board of Veterans’ Appeals decisions under, each with the number of vetted decisions, grants, and remands (full-corpus counts) and the body-system category. Use this to discover which conditions have data, to get the exact slug for get_condition_report, or to compare how common / how winnable different conditions are. Counts reflect only quality-filtered, publicly visible decisions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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

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

Annotations already indicate read-only and idempotent; description adds critical context that counts reflect quality-filtered, publicly visible decisions, enhancing transparency beyond annotations.

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?

Two sentences with no wasted words, each sentence providing essential information about purpose, usage, and data scope.

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 zero parameters and output schema presence, description covers purpose, usage, and data quality notes fully. No gaps identified.

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?

No parameters in schema (0 required), so description does not need parameter details. Baseline set to 4 for zero-parameter tools.

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 lists standardized conditions with counts and body-system categories, distinguishing it from related tools like 'get_condition_report' by mentioning slug retrieval.

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?

Provides explicit use cases: discovering conditions, getting slugs, comparing prevalence or win rates. Does not include when-not-to-use, but context with sibling tools implies alternatives.

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