Skip to main content
Glama

Search case law and regulations

search_legal_authority
Read-onlyIdempotent

Use this when a question calls for the text of a VA rating regulation, the wording of a legal standard, or case law, searched by keyword, by exact citation, or by diagnostic code. Returns 38 CFR rating criteria for matching conditions; doctrine entries quoted verbatim from the regulation, statute or decision they come from, each with pinpoint citations, the date the text was captured, when that text took effect, and the reviewed holdings that construe it; and excerpts from Court of Appeals for Veterans Claims decisions with docket number, case name and relevance score. CAVC decisions are binding precedent for the Board of Veterans' Appeals. The citation parameter takes a section such as "3.310", "38 CFR 3.310(b)" or "38 U.S.C. 5107(b)", and a citation that cannot be read as a section matches nothing rather than being guessed at. A citation on its own is a complete call: query is optional when citation is supplied, and a call carries query, citation, or both. The limit parameter caps results per source, default 5 and maximum 10; the doctrine block is capped at four entries per response and reports the true total. The status field describes the answer in one of four words. "ok" means every component answered and this response carries each matched result it selected. "partial" means a matched result is missing from it, whether shed for the size budget, withheld as a criterion text too long to fit, or unreachable because a component could not complete its search. "no_match" means every component answered and none of them matched. "unavailable" means a component did not answer, so nothing in that response is readable as an absence of authority. statusReason gives the reason for that word in one sentence, derived from the same values as the word itself. A truncation object reports what was shortened, whatever the status: doctrinePropositionsTrimmed counts entries serving their first propositions while reporting their own true total, textBounded says a criterion text was withheld whole rather than cut, and resultsDropped counts the matched results this response does not carry, under regulatory, caseLaw and doctrine. Shortening that keeps every selected result arrives as status "ok" with truncation populated. Docket numbers and case names come only from the returned results, and when the case-law corpus is empty the response says so and returns the regulatory and doctrine results alone. When a response would exceed its size budget it sheds results rather than overrunning, reports responseTrimmedForSize alongside the true totals, and withholds a criterion text too long to fit whole rather than cutting it: that row carries criteriaOmitted and the length of what was withheld, so a partial rule does not arrive as a complete one. citationResolved says whether any source carries the citation supplied: true on positive evidence, false only where the corpus-wide membership scan completed and nothing named the section, and null where that scan did not complete, which is an open question rather than a finding of absence. citationStatus renders the same answer as resolved, unresolved, unknown, unparsed or not_supplied. The coverage block reports how far the search reached: citationScanComplete for that membership question, candidateScansComplete with incompleteCandidateScans for components whose scan window filled before every candidate was examined, truncatedComponents for the sources whose results were shortened, doctrineMatchedOn for whether the doctrine entries came from the citation, the query or the standing authorities, and searchComplete for the conjunction of all of it. totalsAreMeasuredCounts says whether the totals count everything that matched; where it is false a zero is bounded by this search rather than by the corpus. It does not read an individual claim, it does not predict how a claim will be decided, and it is not legal advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 5, max 10).
queryNoSearch query (e.g., "PTSD secondary to MST", "DC 8100 migraine 50 percent criteria", "CUE in combined rating calculation"). Optional when citation is supplied; supply query, citation, or both.
citationNoExact citation to look up (e.g., "3.310", "38 CFR 3.310(b)", "4.16", "38 U.S.C. 5107(b)"). Sufficient on its own: a call with only a citation is answered as a citation lookup. A citation that cannot be read as a CFR or USC section matches nothing and is reported.
diagnosticCodeNoFilter by diagnostic code (e.g., "8100").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / citation / description
      Previous value: -"Exact citation to look up (e.g., \"3.310\", \"38 CFR 3.310(b)\", \"4.16\", \"38 U.S.C. 5107(b)\"). A citation that cannot be read as a CFR or USC section matches nothing and is reported."New value: +"Exact citation to look up (e.g., \"3.310\", \"38 CFR 3.310(b)\", \"4.16\", \"38 U.S.C. 5107(b)\"). Sufficient on its own: a call with only a citation is answered as a citation lookup. A citation that cannot be read as a CFR or USC section matches nothing and is reported."
    • changedInput schema / properties / query / description
      Previous value: -"Search query (e.g., \"PTSD secondary to MST\", \"DC 8100 migraine 50 percent criteria\", \"CUE in combined rating calculation\")."New value: +"Search query (e.g., \"PTSD secondary to MST\", \"DC 8100 migraine 50 percent criteria\", \"CUE in combined rating calculation\"). Optional when citation is supplied; supply query, citation, or both."
    • removedInput schema / required
      Removed value: -[
      -  "query"
      -]
  2. Changed1 schema field changed
    • addedInput schema / properties / citation
      Added value: +{
      +  "description": "Exact citation to look up (e.g., \"3.310\", \"38 CFR 3.310(b)\", \"4.16\", \"38 U.S.C. 5107(b)\"). A citation that cannot be read as a CFR or USC section matches nothing and is reported.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond them: size-budget shedding, whole-criterion withholding vs truncation, the four status values, citationResolved null-vs-false semantics, and the coverage/truncation blocks. This is exactly the extra context annotations cannot supply.

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

Conciseness3/5

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

It is front-loaded with the usage trigger and the response-contract detail is justified by the absence of an output schema, but the body is roughly 500 words and repeats citation-matching behavior more than once ('matches nothing' / citationResolved / citationStatus / citationScanComplete restate the same fact). A tighter pass could cut length without losing meaning.

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 and a fairly complex multi-source response, the description carries the entire return-value burden and does so thoroughly (status, statusReason, truncation, coverage, citation resolution, and the empty-case-law behavior). An agent has enough to interpret any response correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: a bare citation is a complete call and query is optional alongside it, an unparseable citation 'matches nothing rather than being guessed at', and limit is per-source with a hard max of 10. These clarify ambiguity the schema alone leaves open.

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 verb and resource ('search ... VA rating regulation ... legal standard ... case law') and enumerates the three lookup modes (keyword, exact citation, diagnostic code). It is unmistakably distinct from the sibling tools, which are calculators, eligibility checks and payment tools rather than textual authority lookups.

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?

It opens with an explicit trigger condition ('Use this when a question calls for the text of a VA rating regulation, the wording of a legal standard, or case law') and closes with scope exclusions ('does not read an individual claim, does not predict how a claim will be decided, is not legal advice'). It stops short of naming a sibling tool as the alternative for adjacent needs, but the exclusions effectively route the agent away from non-search tasks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources