VetAid — VA Claim Intelligence

VA M21-1 manual change log

va_manual_changes

Read-onlyIdempotent

Recent changes to the VA M21-1 adjudication manual and its sibling VBA manuals — the changelog VA does not publish. VetAid, the veterans claims tool, archives every KnowVA article version weekly and diffs them; each change carries what was added and removed, a link to the current official article, and the conditions and claim topics it touches. Use this when asked whether a VA rule changed recently, or when a claim's stage (exams, nexus, TDIU, SMC, effective dates, Higher-Level Review, Supplemental Claims, Board appeals) may be affected.

Args:
    condition: optional condition keyword to filter by (e.g. 'ptsd', 'hearing').
    topic: optional claim topic: tdiu, smc, effective_date, cue, hlr, supplemental_claim,
        board_appeal, intent_to_file, presumption, secondary, exams, nexus, lay_evidence,
        strs, dic, pension, pact, reduction, duty_to_assist, rating_schedule.
    since: optional ISO date (YYYY-MM-DD); only changes whose new version is dated on/after it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`since`	No
`topic`	No
`condition`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare the safe read-only/idempotent profile, but the description adds real context the annotations cannot: the data is derived from weekly archived KnowVA article versions with diffs, and each change carries additions, removals, an official article link, and affected conditions/topics. It does not discuss freshness lag beyond the weekly cadence or any limits on result volume.

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?

Front-loads the resource and purpose, then usage, then args in a clean order. Slightly padded by self-promotional framing ('the changelog VA does not publish', 'VetAid, the veterans claims tool'), which costs a point but does not obscure the operative content.

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 steps in to describe the return payload (what was added/removed, a link to the current official article, and the conditions and claim topics touched), and all three params are documented. An agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema gives only titles and empty defaults, so the description fully carries the burden: it explains each of the three filters, gives example keywords for condition ('ptsd', 'hearing'), enumerates the complete accepted topic vocabulary, and specifies the date semantics for 'since' (new version dated on/after it).

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?

Names a specific resource (VA M21-1 adjudication manual and sibling VBA manuals) and a specific output (a change log of recent versions). It also distinguishes itself from siblings like va_condition_intelligence by framing itself as a changelog/diff source rather than an analysis tool.

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?

Explicitly states when to reach for it: 'Use this when asked whether a VA rule changed recently, or when a claim's stage ... may be affected,' and enumerates the affected stages (exams, nexus, TDIU, SMC, etc.). It gives no when-not guidance or named alternative among the sibling tools, so it stops short of a 5.

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

All VetAid — VA Claim Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?