Skip to main content
Glama

Find secondary conditions

find_secondary_conditions
Read-onlyIdempotent

Use this when a veteran names a VA service-connected condition and asks what other conditions can follow from it. It does not diagnose, establish that a particular veteran's condition is secondary, or supply the medical nexus opinion a secondary claim needs. Returns the records whose own primary condition is the one searched for, each with evidence strength, medical rationale, key studies, filing notes, diagnostic codes and the primary condition the record itself names. Other primaries the search terms reached are summarised under relatedPrimaries, with the matched term and a count, not returned as rows. Each row carries provenance: the 38 CFR 3.310 paragraph the link rests on, the rating schedule section and code, their eCFR URLs, and the date codes and percentages were checked against the schedule, which is a question of validity, not of whether a code fits a particular veteran. The key studies were drafted from published research and have not been verified citation by citation, which every row states in its provenance note. limit sets the records per response, default 5 and maximum 15, and offset skips records of the same result, default 0 and maximum 100000. Records are ordered by strength of evidence and then by their primary and secondary condition names, the same on every call. Past a budget of about 12 KB the last records are left out whole rather than shortened (at least one is kept) and responseTrimmedForSize is true. totalExactCount counts every record on file, count and exactCount those returned; hasMore says more follow and nextOffset fetches them, null when none do. relatedPrimaries is returned whole on every response. A totalExactCount of 0 means nothing is on file for that search term, not that no link exists. An offset past the last record returns no records, while totalExactCount still counts the records on file.

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": {
      "primaryCondition": "<primaryCondition>"
    },
    "name": "find_secondary_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many secondary-condition records one response carries, 1 to 15, default 5. A response is also held to a size budget of about 12 KB, so it can carry fewer records than the limit, whole ones only; responseTrimmedForSize is then true and nextOffset gives the offset of the first record it left out.
offsetNoHow many records of the same result to skip before the first one returned, 0 to 100000, default 0. Records keep the same order on every call, so the nextOffset one response reports returns the records that follow it.
primaryConditionYesPrimary service-connected condition to search against (e.g., "PTSD", "Lumbar strain"). Partial matches supported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "How many secondary-condition records one response carries, 1 to 15, default 5. A response is also held to a size budget of about 12 KB, so it can carry fewer records than the limit, whole ones only; responseTrimmedForSize is then true and nextOffset gives the offset of the first record it left out.",
      +  "maximum": 15,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "How many records of the same result to skip before the first one returned, 0 to 100000, default 0. Records keep the same order on every call, so the nextOffset one response reports returns the records that follow it.",
      +  "maximum": 100000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description goes well beyond that: provenance (38 CFR 3.310 paragraph, rating schedule section and code, eCFR URLs, check dates), an unverified-citations caveat repeated per row, deterministic ordering, a 12 KB trim budget that drops whole records and sets responseTrimmedForSize, and pagination via hasMore/nextOffset. This is unusually rich disclosure for a read-only lookup.

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?

Front-loaded with the usage trigger, then result shape, then pagination, with no filler or marketing language. It is long and repeats the limit/offset semantics already in the schema, which keeps a sentence or two from fully earning their place.

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?

There is no output schema, so the description has to carry the return contract, and it does: row fields, relatedPrimaries summarisation, provenance, trimming flag, totalExactCount vs count, and the meaning of a zero count. An agent has everything needed to call and interpret this tool.

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 description coverage is 100% and the limit/offset schema descriptions already explain the size budget, trimming, defaults, ranges and nextOffset. The description largely restates that, adding only the ordering rule and the edge case that an offset past the last record yields no rows while totalExactCount still counts. Baseline 3 is right when the schema does the heavy lifting.

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?

States a specific verb and resource (find secondary conditions for a named primary condition) and pins the scope precisely: it returns records keyed to the searched primary, not diagnoses or nexus opinions. An agent can tell from the first sentence that this is a reference lookup, not a case adjudication.

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?

Gives an explicit trigger ('when a veteran names a VA service-connected condition and asks what other conditions can follow from it') and explicit exclusions (does not diagnose, does not establish a specific veteran's secondary condition, does not supply a nexus opinion). It never names an alternative sibling tool to use instead, so it stops short of the 5 level.

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