VetAid — VA Claim Intelligence

Get my case analysis

get_my_case_analysis

Read-onlyIdempotent

Get a per-stage analysis SUMMARY for one of the veteran's OWN cases (read-only; never runs a paid analysis). Requires the veteran's personal VetAid agent key in the request's Authorization header (Bearer vak_...). Returns 'not found' for any case the key owner does not own — no cross-user access.

Args:
    case_id: The id of one of the veteran's own cases (from list_my_va_cases).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`case_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds materially important behavior: it never triggers a paid analysis, requires a specific Authorization header format, and returns 'not found' for non-owned cases to prevent cross-user access. This goes well beyond what annotations alone communicate.

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 front-loaded with the most decision-relevant facts (summary, read-only, no paid analysis) and every sentence adds value. The Args block is concise and directly clarifies the only parameter.

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?

For a single-parameter, read-only tool with strong annotations, the description covers purpose, auth requirements, ownership boundary, return behavior for unauthorized access, and argument sourcing. Nothing an agent needs to correctly select and invoke this tool is missing.

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 description coverage is 0%, but the description fully compensates for the single parameter. It explains that case_id must be one of the veteran's own cases and references list_my_va_cases as the source, adding meaning the schema's bare 'Case Id' field does not provide.

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 states a specific action ('Get a per-stage analysis SUMMARY'), a clear resource ('one of the veteran's OWN cases'), and a distinguishing constraint ('read-only; never runs a paid analysis'). This clearly separates it from the paid sibling run_my_case_analysis even without naming it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit context for when this tool is appropriate: for a read-only per-stage summary, never a paid analysis. It also names the source of the required case_id ('from list_my_va_cases') and the authentication prerequisite (VetAid agent Bearer key), giving an agent clear decision and invocation guidance.

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

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.4/5.0

Disambiguation3/5

Most tools have clear individual roles, and the personal workflow tools are unambiguous. However, va_condition_intelligence overlaps with va_denial_stats, va_evidence_that_wins, and va_top_authorities, since it also reports outcome shares, evidence associations, and cited authorities, so selecting the right tool often depends on carefully reading the long descriptions.

Naming Consistency4/5

All names use lower_snake_case and are readable, with a consistent verb-first pattern for personal tools (get_my_*, list_my_*, run_my_*) and a va_ prefix for public data tools. The mix of verb-first and noun-phrase names is a minor inconsistency, but the two families are predictable and internally consistent.

Tool Count5/5

Nine tools is a well-scoped count for this domain. Each tool maps to a meaningful operation: four cover the personal case-analysis workflow and five cover aggregate VA data intelligence, with no obvious bloat at the tool-count level.

Completeness4/5

The surface covers the core lifecycle: list cases, check credits, run an analysis, retrieve the analysis summary, and query the main public intelligence areas (outcomes, evidence, authorities, and manual changes). Minor gaps exist, such as no explicit analysis-status endpoint for the 5-8 minute run and no separate condition-level denial-reason tool, but agents can work around these.

Resources

Need Help?