Skip to main content
Glama

bva-corpus

by com.veterans-rights
OverviewDiscussionsAdmin

Condition report

get_condition_report
Read-onlyIdempotent

For a single condition (by slug like "ptsd" or "sleep-apnea", or by common name/alias like "PTSD", "acid reflux", "ringing in the ears"), return a full corpus-grounded report: how Board decisions mentioning it turned out (whole-decision granted / partly granted / remanded / denied), decision-level service-connection theory labels, an explicit decision-level attribution limitation and a notice that unverified extracted ratings are withheld, and — when available — a plain-English, source-cited summary of how the VA defines and rates the condition. The richest single call for "tell me about VA claims for ". Educational statistics, not a prediction or legal advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conditionYesCondition slug (e.g. "ptsd", "sleep-apnea") or a common name/alias (e.g. "PTSD", "acid reflux").
example_limitNo

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds substantial behavioral context beyond those: the report is corpus-grounded, includes a decision-level attribution limitation, withholds unverified extracted ratings, is educational (not prediction or legal advice), and may include source-cited summaries. These are valuable disclosures that help an agent set user expectations and understand limitations. No contradiction with 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?

The description is dense yet efficient, packing a high amount of meaningful information into a compact structure. It front-loads the core action and result, then enumerates contents and caveats. Every clause adds value: scoping, content list, limitation, withheld data, source-cited summary, and the educational/prediction caveat. No redundant or filler words.

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 the description does not need to detail return fields. It covers the tool's purpose, content, limitations, and usage context well. The only notable gap is that example_limit is not explained anywhere, though it is optional with a default and the output schema may clarify its effect. For a complex report tool, the description is otherwise very complete.

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

Parameters2/5

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

Schema coverage is only 50% (condition has a description, example_limit does not). The description repeats the condition parameter's slug/alias semantics but adds nothing new for either parameter. Crucially, it does not explain what example_limit controls (e.g., number of examples or case listings), leaving a gap that the schema also fails to fill. Since coverage is low, the description should compensate but does not.

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: 'return a full corpus-grounded report' for a single condition. It enumerates the report's components (outcomes, theory labels, attribution limitation, withheld ratings, source-cited summary) and explicitly differentiates from siblings by calling itself 'The richest single call for "tell me about VA claims for <condition>"'. This leaves no ambiguity about what the tool does or how it differs from sibling tools.

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?

The description gives a clear usage context ('The richest single call for ...') which implies using this tool when a comprehensive condition overview is needed. However, it does not explicitly name alternative tools or state when not to use it, e.g., for searching individual decisions. This falls just short of explicit when/when-not guidance, but the context is clear enough for an agent to infer appropriate use.

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
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