bva-corpus

Find an accredited representative

find_accredited_rep

Read-onlyIdempotent

Find a VA-accredited representative to help with a disability claim or appeal. Choose an accredited representative: VSO (Veterans Service Organization) representatives — who help FREE — plus accredited claims agents and accredited attorneys. This tool leads with free options first. Returns representatives filtered by state, city and type. Attorneys/agents may generally charge for review after notice of the initial VA decision, subject to fee rules and a written agreement. Not legal advice; not affiliated with the VA.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No
`limit`	No
`state`	No	US state (2-letter code or full name).
`rep_type`	No

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Tool-specific result payload.
`link`	Yes	Tagged deep link into the matching veterans-rights.com page.
`disclaimer`	Yes	Standing not-legal-advice / not-VA framing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 15, 2026
- changedInput schema / required
```
Previous value: -[
-  "limit"
-]New value: +[]
```
Changed1 schema field changedJun 20, 2026
- removedInput schema / properties / language
```
Removed value: -{
-  "maxLength": 40,
-  "type": "string"
-}
```

Changed1 schema field changedJun 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result payload.",
+      "type": "object"
+    },
+    "disclaimer": {
+      "description": "Standing not-legal-advice / not-VA framing.",
+      "type": "string"
+    },
+    "link": {
+      "description": "Tagged deep link into the matching veterans-rights.com page.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "data",
+    "link",
+    "disclaimer"
+  ],
+  "type": "object"
+}

First observedJun 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, and the description adds real context beyond them: VSO help is free, attorneys/agents may charge after notice of the initial decision under fee rules, and it is not legal advice nor VA-affiliated. It does not disclose pagination or result-ordering behavior, but the added domain caveats are substantive.

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?

Purpose and the free-first framing are front-loaded, and each sentence carries information (rep types, fee rules, disclaimer). The legal disclaimer tail is a little long for a lookup tool, but nothing is redundant.

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?

An output schema exists, so return values need not be explained, and the description covers what the tool does, the filter dimensions and the rep taxonomy. The main gap is the undocumented limit parameter and any hint about result ordering, which is minor given the output schema.

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 coverage is only 25% (just 'state' is documented), so the description must carry weight. It maps the filters to 'state, city and type' and names the rep categories that correspond to the rep_type enum, but says nothing about the limit parameter or the maxLength constraints, leaving part of the coverage gap unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Find a VA-accredited representative to help with a disability claim or appeal') and enumerates the three rep categories, so the tool's scope is unambiguous. Sibling differentiation is implicit only — the other tools concern conditions, ratings and appeals, so no explicit routing is needed, but none is provided either.

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

Usage Guidelines3/5

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

It gives in-tool guidance ('leads with free options first', attorneys/agents charge after the initial decision subject to fee rules and a written agreement), which helps pick a rep_type. It never states when to reach for this tool versus a sibling, nor any exclusions or prerequisites, so usage remains implied.

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

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