Find secondary conditions
find_secondary_conditionsUse 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
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 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. | |
| offset | No | 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. | |
| primaryCondition | Yes | Primary service-connected condition to search against (e.g., "PTSD", "Lumbar strain"). Partial matches supported. |