Skip to main content
Glama

Find similar appeals

find_similar_appeals
Read-onlyIdempotent

Find source-linked recent Board decisions mentioning one or more canonical conditions. Resolves exact names, slugs and aliases; inspects at most the 50 most recent indexed decisions per condition, then applies optional decision-level filters. Results are research examples, not a representative sample, complete filtered cohort, condition-specific outcomes or chances of winning. Grant rates are withheld. Verify each issue against the original Board decision.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "conditions": "<conditions>"
    },
    "name": "find_similar_appeals"
  }
}

Input Schema

NameRequiredDescriptionDefault
conditionsYesCanonical names, slugs or exact aliases, e.g. ["PTSD", "tinnitus"]. Matches any supplied condition.
is_pact_actNo
sample_limitNo
exposure_basisNo
service_connection_theoryNo

Output 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
    • changedInput schema / properties / conditions / description
      Previous value: -"Canonical names, slugs or exact aliases, e.g. [\"PTSD\", \"tinnitus\"]. Matches ANY supplied condition. Use list_conditions to discover valid slugs."New value: +"Canonical names, slugs or exact aliases, e.g. [\"PTSD\", \"tinnitus\"]. Matches any supplied condition."
  2. Changed7 schema fields changed
    • removedInput schema / properties / conditions / default
      Removed value: -[]
    • changedInput schema / properties / conditions / description
      Previous value: -"Claimed conditions, e.g. [\"PTSD\",\"tinnitus\"]. The strongest similarity signal."New value: +"Canonical names, slugs or exact aliases, e.g. [\"PTSD\", \"tinnitus\"]. Matches ANY supplied condition. Use list_conditions to discover valid slugs."
    • addedInput schema / properties / conditions / items / maxLength
      Added value: +80
    • addedInput schema / properties / conditions / items / minLength
      Added value: +1
    • addedInput schema / properties / conditions / maxItems
      Added value: +5
    • addedInput schema / properties / conditions / minItems
      Added value: +1
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "conditions"
      +]
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "conditions"
      -]New value: +[]
  4. 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"
      +}
  5. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations only declare read-only, idempotent, closed-world behavior; the description goes well beyond by disclosing the 50-most-recent-decisions-per-condition crawl cap, the alias/slug resolution step, the application of optional decision-level filters, and the deliberate withholding of grant rates. It also sets explicit expectations that results are examples, not a complete filtered cohort, which prevents an agent from over-claiming.

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?

Four dense sentences, each earning its place: scope first, then lookup/scan behavior, then the epistemic caveat about the sample, then verification guidance. No redundant restatement of the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value shape need not be explained, and the safety profile is covered by annotations. However, for a 5-parameter tool with only 20% schema coverage, the description leaves three filter parameters and the sample-limit semantics undefined, which is a real gap for correct invocation.

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 description coverage is only 20%, so the description must carry the parameter burden, but it only glosses conditions (names/slugs/aliases are covered in the schema itself) and vaguely refers to 'optional decision-level filters' without naming is_pact_act, exposure_basis, service_connection_theory, or what sample_limit does relative to the 50-decision inspection cap. The enum values self-document somewhat, but the interaction between the inspection pool and sample_limit is left unexplained.

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 names a specific verb and resource — 'Find source-linked recent Board decisions mentioning one or more canonical conditions' — and states the lookup mode (resolves names, slugs, aliases). It is clear what the tool returns, though it never contrasts itself with the sibling search_bva_decisions, so an agent must infer the split.

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?

Usage is implied by the scope statement (example decisions per condition) rather than stated outright; no sibling alternative or when-not-to-use rule is given. The 'results are research examples, not a representative sample...' sentence is valuable interpretive guidance but governs reading the output, not choosing the tool.

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