このMCPでできること
Provides VA disability rating calculations, compensation estimates, presumptive and secondary-condition lookups, exam preparation, and cited legal authority searches.
機能
ツール
13
ツール
analyze_rating_gap
Analyze a rating gap
Use this when a veteran gives a condition name and the percentage currently assigned for it, and wants that percentage compared against the VASRD criteria. Returns the tier that matches the current percentage, the next tier above it, and every higher tier on file for that condition, with the criteria each one requires. It reports when the condition is already at the highest documented tier, and when no criteria are on file for that condition name. documentedTiers lists the tier percentages on file for the condition, and currentPercentIsDocumentedTier says whether the percentage supplied is one of them: false means the figure does not correspond to a tier in the criteria on file, which happens when the rating came from a formula or a code this search did not resolve. For a veteran at zero percent, zeroPercentBasis is "documented" when a zero percent row for the code is on file and "unresolved" when the complete tier set could not be established, and zeroPercentUnderFourThirtyOne answers whether 38 CFR 4.31 is what assigns that zero: false where the schedule on file provides a zero percent evaluation or the rating is compensable, and null where the question is open. A null there is an unanswered question rather than a finding that 4.31 applies, because the rule turns on what the schedule provides for the code and this tool reads the criteria on file rather than the omissions in the schedule. It describes what the criteria require; only VA decides a rating.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['conditionName', 'currentPercent'], 'properties': {'conditionName': {'type': 'string', 'description': 'Condition to analyze (e.g., "PTSD", "Lumbar strain").'}, 'currentPercent': {'type': 'number', 'description': 'Current VA rating percentage for this condition (e.g., 30, 50, 70).'}}}
calculate_combined_rating
Calculate combined VA rating
Use this when a veteran has two or more VA disability rating percentages and wants the combined rating. Applies the 38 CFR 4.25 Combined Ratings Table procedure: pairwise combination in severity order, whole-percent rounding after each step, then conversion to the nearest 10. Returns combinedRating as an object holding both figures under their own names: rounded is the rating after that conversion, raw is the Combined Ratings Table value before it. The arithmetic for each step comes back alongside them. The optional bilateral argument tags the ratings that affect both arms or both legs; when it is supplied and one pair has a compensable rating on each side, 38 CFR 4.26 applies to those ratings first: they combine with each other, 10 percent of that value is added rather than combined, and the result enters the 4.25 combination as one disability. Without that argument no bilateral factor is applied. The 38 CFR 4.26(d) comparison across eligible groupings is exhaustive here for up to 16 tagged compensable ratings; past that the response carries combinedRatingWithoutBilateralFactor in place of combinedRating, labelled as a figure the bilateral factor has not been applied to, with a note that VA and accredited representatives compute that factor. The result differs from adding the percentages and from a simple product. It reports what 38 CFR 4.25 and 4.26 yield for the percentages supplied, not what VA has assigned, and it does not evaluate special monthly compensation.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['ratings'], 'properties': {'ratings': {'type': 'array', 'items': {'type': 'number', 'maximum': 100, 'minimum': 0}, 'maxItems': 20, 'description': 'Array of individual disability rating percentages (0-100), e.g., [70, 50].'}, 'bilateral': {'type': 'array', 'items': {'type': 'object', 'required': ['index', 'extremity'], 'properties': {'index': {'type': 'integer', 'maximum': 19, 'minimum': 0, 'description': 'Position in the ratings array of the rating this entry describes (0-based).'}, 'extremity': {'enum': ['left-arm', 'right-arm', 'left-leg', 'right-leg'], 'type': 'string', 'description': 'The extremity that rating affects.'}}, 'additionalProperties': False}, 'maxItems': 20, 'description': 'Optional. Tags the ratings that affect a paired extremity, so 38 CFR 4.26 can be applied: those ratings are combined with each other first, 10 percent of that value is added (not combined), and the result enters the 4.25 combination as one disability. The factor needs a compensable rating on both sides of one pair (both arms or both legs); tag every rating that affects an arm or a leg and the tool applies the factor only where the regulation allows it. Tagging more than 16 compensable ratings is accepted and answered, but past that the 38 CFR 4.26(d) comparison across eligible groupings is not exhaustive here, so the result carries the 4.25 combination of every rating supplied under combinedRatingWithoutBilateralFactor instead of a combined rating, and says where the complete calculation comes from.'}}}
calculate_rolling_window
Check a 12-month absence window
Use this when a veteran supplies dates of incapacitating episodes and the question involves the 38 CFR 4.71a formula for rating intervertebral disc syndrome on incapacitating episodes, diagnostic code 5243. Totals the calendar duration of those episodes inside the 12 months ending on a reference date: the window opens the day after the same date one year earlier and closes on the reference date, with both ends counted, so an episode that began exactly 12 months before that date falls outside it by one day. That formula bands on total calendar duration in weeks, so weekend and holiday days inside an episode count, and only periods flagged as bed rest prescribed by a physician count toward a tier. Returns the window, a per-period breakdown, the tier the flagged episodes would support, and a separate employer-leave workday count that plays no part in that tier. Inside ivdsThresholdAnalysis, calendarDaysBelow60PercentThreshold and weeksBelow60PercentThreshold report how far the counted episodes fall below the 6-week duration that bands at 60 percent under that formula. They measure the reported history against a threshold in the regulation; they are not a target, since a veteran does not accumulate bed rest to reach a rating. The tier it reports is an estimate from the episodes supplied. It does not decide FMLA entitlement and does not apply to conditions rated outside diagnostic code 5243.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['absencePeriods'], 'properties': {'referenceDate': {'type': 'string', 'description': 'The reference date for the 12-month rolling window (YYYY-MM-DD). Defaults to today. Typically the anticipated C&P exam date. Must be a real calendar date; an unparseable value is rejected.'}, 'absencePeriods': {'type': 'array', 'items': {'type': 'object', 'required': ['startDate'], 'properties': {'endDate': {'type': 'string', 'description': 'End date of the absence period in YYYY-MM-DD format. If omitted, assumed same as startDate (single day). Must be on or after startDate; a reversed range is rejected rather than counted.'}, 'dayCount': {'type': 'number', 'description': 'Total CALENDAR days absent in this period, weekends included, for a period reported as a count (for example "20 days between March and December") rather than as exact dates. If provided, startDate/endDate define the outer span and dayCount overrides the calendar days counted within it. A work-day total alone does not establish calendar duration: this value is a reported calendar-day total, not an estimate converted from work days.'}, 'startDate': {'type': 'string', 'description': 'Start date of the absence period in YYYY-MM-DD format.'}, 'physicianPrescribedBedRest': {'type': 'boolean', 'description': "True only when a physician PRESCRIBED bed rest for this period and treated the veteran, which is what 38 CFR 4.71a Note (1) requires of an incapacitating episode. Optional; when omitted or false the period is reported as a plain absence and contributes NOTHING to the IVDS tier. A work absence, a sick day, or self-directed rest without a physician's prescription does not meet that definition."}}}, 'description': 'Array of absence periods. Each must have at least a startDate.'}}}
check_presumptive_eligibility
Check presumptive eligibility
Use this when a veteran asks whether a condition is presumptively service connected, or which conditions are presumptive for a given exposure or service era. Returns matching presumptive conditions with the service era, exposure type, required service, legal authority and evidence needed for each, and repeats that legal authority in a provenance block on every row, with the date the presumption took effect where one date is true of the whole row; that date can be null for a row that groups conditions added on different dates. At least one of condition, serviceEra or exposureType is required. Filters combine with AND: condition plus exposureType or serviceEra narrows to their intersection, and each filter needs at least one word of three or more characters or the query is refused. A condition description that names a qualifying circumstance, such as a diagnosis that has to come after the qualifying service, states a limit of the presumption rather than a detail beside it. An empty result means no entry satisfies that exact combination, not that the condition is non-presumptive. Whether a particular veteran meets the service requirement depends on service records this tool does not read.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': [], 'properties': {'condition': {'type': 'string', 'description': 'Condition to check for presumptive status (e.g., "Parkinson\'s disease", "Hypertension").'}, 'serviceEra': {'type': 'string', 'description': 'Service era or conflict (e.g., "Vietnam", "Gulf War", "Post-9/11") for era-specific presumptives.'}, 'exposureType': {'type': 'string', 'description': 'Known toxic/environmental exposure (e.g., "Agent Orange", "burn pits", "Camp Lejeune water").'}}}
compare_rating_criteria
Compare rating criteria
Use this when a veteran names a VA diagnostic code and wants the rating criteria for it. Returns the VASRD criteria on file for that code at every tier, highest percentage first, with the condition name, body system and 38 CFR reference, so the findings each tier requires can be read side by side. It takes a diagnostic code rather than a condition name. A code that 38 CFR 4.71a, 4.73 or 4.124a rates in two columns, one for the dominant arm (Major) and one for the non-dominant arm (Minor), returns the regulation's own table and an empty tiers list: schedule is that table as published, with schemaVersion, variant and provenance (the eCFR edition date and the SHA-256 of the source text), every row carrying both published percentages, and scheduleText renders it with its headings, footnotes and the notes whose stated scope includes the code. Notes printed in the same table whose applicability is not established are quoted in a separate labelled section; placement alone does not establish that they apply to this code. For a neuritis or neuralgia code rated on one of those nerve scales, schedule lists each maximum with its qualifying text and ratedOnScale is the scale. The response lists every row and every maximum without choosing one, and when that table cannot be read it carries a message and a link to the eCFR section instead, even with no criteria on file. Other codes with no criteria on file return an empty result. Every response carries a source block: the 38 CFR reference for the code, a link to the current rating schedule at the publisher, and a scheduleSnapshot whose retrievedAt is the date this text was read from eCFR. That date is null for the criteria on file, with a note saying it is not recorded, so the criteria are usable as the schedule on file and the current text governs where the two differ; for a table under schedule it is the date the snapshot was read. It is not a lookup of what a rating pays and it does not combine ratings.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['diagnosticCode'], 'properties': {'diagnosticCode': {'type': 'string', 'description': 'VA diagnostic code (e.g., "8100" for migraines, "5260" for knee).'}}}
compute_retroactive_pay
Estimate retroactive back pay
Use this when a veteran gives an effective date and a rating increase and asks what the retroactive amount would be. Returns an estimate of the difference in monthly compensation for each month of the period, with a per-month breakdown, the assumptions behind it, and its own disclaimer. Under 38 CFR 3.31 payment starts on the first day of the month FOLLOWING the month the award became effective, with no exception when the effective date is itself the first of a month, and the period runs through the month of adjudication, which is counted in full. VA rate tables take effect on December 1, so a payment year runs from December 1 through November 30 and December of one year is paid at the next payment year rates. Each month of the breakdown reports the payment year it was paid from (rateYear), that table effective date (rateTableEffectiveDate) and where the table came from (rateSource), and the tables the period drew on are listed once each in rateTables; a published table carries the VA page it was transcribed from, and a reconstructed table carries none, because it is derived rather than transcribed. Monthly rates for payment years 2000 onward are read from VA published rate tables; earlier years are reconstructed from the current published table back-adjusted by the SSA cost-of-living chain, and the result states which of the two the requested period used. A month past the newest published table is served from the newest one available, and the result then reports totalIsExact false with incompleteReason naming those months. The total is an estimate either way, because dependent status is taken as constant across the period. It handles an increase only: the new rating has to be higher than the previous one, and effective dates before 1990 are refused. It does not set an effective date and it does not report an amount VA has authorized.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['effectiveDate', 'fromRating', 'toRating', 'hasSpouse', 'dependentCount'], 'properties': {'isTdiu': {'type': 'boolean', 'description': 'Whether the new rating includes TDIU (treats as 100% for $).'}, 'toRating': {'type': 'number', 'description': 'New VA rating percentage (0-100).'}, 'hasSpouse': {'type': 'boolean', 'description': 'Whether the veteran was married during the period.'}, 'fromRating': {'type': 'number', 'description': 'Previous VA rating percentage (0-100).'}, 'effectiveDate': {'type': 'string', 'description': 'ISO date YYYY-MM-DD of rating change effective date.'}, 'dependentCount': {'type': 'number', 'description': 'Number of dependent children under 18.'}, 'adjudicationDate': {'type': 'string', 'description': 'ISO date the rating decision was issued. Defaults to today.'}}}
find_claim_help
Find free and accredited claim help
Use this when a veteran asks who can help them with a VA disability claim, or when they describe a crisis. The Veterans Crisis Line comes first, in full, when need is crisis, and no other need returns crisis content. Setting urgent true puts the veteran’s first action at the top of routeNow and does not change the crisis routing. Every result carries accredited representation routes: VA accredited Veterans Service Organizations, whose services on VA benefit claims are free, and accredited attorneys and claims agents, who may charge fees only for representation provided after VA issues notice of an initial decision on the claim (38 CFR 14.636(c) and 38 U.S.C. 5904(c)(1)). It also returns the VA Office of General Counsel accreditation search and the VA.gov find a representative tool, the state or territory veterans agency matching a two-letter state code, VA phone numbers suited to the need, the documents worth bringing, and links to the VA forms that need points at. It names no individual, firm or private directory. It does not prepare, submit or file any form, and it reads no account data, so the answer is the same for every caller with the same inputs. A two-letter code with no agency on file returns stateAgency null and coverage.stateResolved false, with the national routes unchanged. The askedFor argument carries the veteran’s own words. It does not change the routing and does not withhold it: a request that this tool or the model calling it act as the veteran’s attorney, agent or representative before VA, a request to supply words for a veteran or a clinician to use, which covers asking for a personal, buddy or lay statement, a statement in support, or a nexus letter the veteran already has to be rewritten, polished, tightened or cleaned up, to choose a decision review lane for the veteran, or to prepare or file a claim returns status ok with the same findings, plus a boundary object whose kind names the primary boundary crossed and whose kinds lists every boundary the request crossed, in the fixed precedence representation_request, then words_for_testimony, then review_lane_choice, then preparation_request, so a request that crosses two keeps both. Its opening, rule and route state what VeteranHQ does not do, one sentence per kind in kinds, the accreditation rule (38 CFR 14.629) and the fee rule (38 CFR 14.636, 38 U.S.C. 5904(c)(1)), and where the work belongs; those instruments are merged into sources and the same paragraph leads message, behind the Veterans Crisis Line when need is crisis. Provenance is indexed rather than repeated: sources is the registry of full references, each with a stable id, and every guidance line and the boundary carry sourceIds into it. A line’s citation is the sources entry whose id it names, and its passage is line.quote when that field is present and that entry’s quote otherwise. An id is the citation for a regulation or statute (38 CFR 14.636(b)), a short slug for a VA page or form (va-find-accredited-rep, va-form-21-526ez), and product-boundary for the one entry that states what VeteranHQ does and does not do, which carries no url because there is no document to open. A form is cited by its number, with its name in title. One kind of provenance is absent from sources and stays on the line as authority: the state veterans agency page, which is one state’s own contact page and changes with the state argument.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['need'], 'properties': {'need': {'enum': ['file_first_claim', 'pending_claim', 'decision_received', 'increase', 'secondary', 'exam', 'representation', 'records', 'crisis', 'general'], 'type': 'string', 'description': 'What the veteran is trying to do. Use general when the veteran has not said, and crisis when they describe a mental health emergency.'}, 'state': {'type': 'string', 'description': 'Two-letter US state or territory code, for example CA, TX or PR. Adds that state veterans agency to the answer. Omit it when the veteran has not said where they live.'}, 'urgent': {'type': 'boolean', 'description': 'True when the request is time sensitive, for example a letter, an exam notice or a date the veteran is worried about. It puts their first action at the top of the answer. It does NOT change the crisis routing: use need crisis when the veteran describes a mental health emergency.'}, 'askedFor': {'type': 'string', 'description': "What the veteran asked for, in their own words, when they are available. It changes nothing about the routing and does not withhold it. A request that this tool act as the veteran's representative, attorney or agent before VA, to prepare or file a claim, to choose a decision review lane for the veteran, or to supply words for a veteran or a clinician to use returns the same answer with a boundary object added, naming what VeteranHQ does not do, the accreditation and fee rules and where the work belongs; its kinds array lists every one of those classes the request crossed, in the precedence representation_request, words_for_testimony, review_lane_choice, preparation_request, and kind is the first of them. Ordinary requests for help are answered with no boundary object."}}}
find_secondary_conditions
Find secondary conditions
Use this when a veteran names a service-connected condition and asks what other conditions can follow from it. Returns the records whose own primary condition is the one searched for, each with the strength of the supporting evidence, the medical rationale, key studies, filing notes, the diagnostic codes involved, and the primary condition the record itself names, so a row can be read against the query it answers. Other primary conditions that the search terms reached are summarised separately under relatedPrimaries, with the term that matched and a count, rather than being returned among the rows. Each row carries its provenance: the paragraph of 38 CFR 3.310 the link rests on, the rating schedule section and diagnostic code its evaluation comes from, the eCFR URLs for those sections, and the date the codes and percentages were checked against the rating schedule. That check establishes that a code exists in the schedule and that an evaluation is one the schedule offers for it, which is a question of validity rather than 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. The limit parameter sets how many records one response carries, default 5 and maximum 15, and offset is how many records of the same result are skipped before the first one returned, default 0 and maximum 100000. Records are ordered by strength of evidence and then by their primary and secondary condition names, so the order is the same on every call. A response is also held to a size budget of about 12 KB: when the records within the limit would exceed it, the last of them are left out whole rather than shortened, a response with any record to serve carries at least one, and responseTrimmedForSize is true. totalExactCount is every record on file for the search, count and exactCount are the records in the response, hasMore says whether any records follow them, and nextOffset is the offset that returns the next records and is null when none follow. 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. It does not diagnose, it does not establish that a particular veteran's condition is secondary, and it does not supply the medical nexus opinion a secondary claim needs.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['primaryCondition'], 'properties': {'limit': {'type': 'integer', 'maximum': 15, 'minimum': 1, '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.'}, 'offset': {'type': 'integer', 'maximum': 100000, 'minimum': 0, '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.'}, 'primaryCondition': {'type': 'string', 'description': 'Primary service-connected condition to search against (e.g., "PTSD", "Lumbar strain"). Partial matches supported.'}}}
get_guide
Read a VeteranHQ guide
Use this when a slug from search_guides names the guide a veteran needs and the answer should carry what the guide says. Returns the slug, title and summary, the date the facts in it were last verified against its sources, the public URL of the guide on veteranhq.app, the body split into the sections the guide itself defines, each with a heading and its text, and the sources the guide cites, each with a title and a URL. A slug this library does not hold returns a tool error carrying GUIDE_NOT_FOUND, whose message says to call search_guides and use a slug from its results. A guide longer than one result can carry returns the sections that fit, plus omittedSections counting the sections left out and a note stating that count and the guide URL. A single section larger than the whole budget is served shortened at a paragraph or sentence boundary, with truncatedSection naming its heading and the note repeating it, so a section that was cut is distinguishable from one served whole. Those three fields are absent when the whole guide is returned, so a shortened answer is distinguishable from a complete one. A guide states the rules as VeteranHQ read them from the cited sources on the date it reports, and VA decides a claim. It reads no account data, so the answer is the same for every caller with the same inputs.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['slug'], 'properties': {'slug': {'type': 'string', 'description': 'The guide to read, as returned in the slug field by search_guides.'}}}
lookup_compensation_rate
Look up monthly compensation rate
Use this when a veteran wants the monthly VA disability compensation amount for a given rating percentage and dependent situation. Returns the monthly and annual amounts from the VA compensation rate table in effect, with the rate year and effective date. The rating is read to the nearest 10 percent, and dependents change the amount only at 30 percent and above. Children are counted as children under 18; school-age children 18 to 23, dependent parents and aid and attendance are outside what it models. It gives the published rate for that combination, not what a specific veteran is paid, and it is not a back-pay calculation for a past period.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['rating'], 'properties': {'rating': {'type': 'number', 'description': 'Disability rating percentage (0–100, rounded to nearest 10).'}, 'hasSpouse': {'type': 'boolean', 'description': 'Whether veteran has a spouse. Affects rates at 30%+. Defaults to false.'}, 'childrenCount': {'type': 'number', 'description': 'Dependent children under 18. Affects rates at 30%+. Defaults to 0.'}}}
prepare_cp_exam
Prepare for a C&P exam
Use this when a veteran has a VA compensation and pension examination scheduled for a condition and wants to know what it involves. Returns the examination type and typical length, what the examiner does, the questions examiners commonly ask, the Disability Benefits Questionnaire sections that apply, and records worth bringing. It does not return advice about what to describe, emphasize or omit at the examination. For a condition with a guide on file it also returns the diagnostic code for that condition and where its rating criteria are published, which are what the examiner's findings are scored against; any other condition returns a general exam guide. Educational reference about the examination process. It does not schedule, reschedule or contact VA, and the examiner's findings and VA decide the rating.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['condition'], 'properties': {'condition': {'type': 'string', 'description': 'Condition being examined (e.g., "PTSD", "knee", "sleep apnea", "tinnitus").'}, 'currentRating': {'type': 'number', 'description': 'Current rating if already rated (for increase exams). Optional.'}}}
search_guides
Search the VeteranHQ guides
Use this when a veteran asks about a VA topic VeteranHQ has written a guide on. Returns the guides whose text matches the query, highest scoring first, each carrying the guide slug, title, summary and public URL, and no body text. The ordering is lexical and deterministic, computed from where each word of the query appears: a match in the guide title scores above one in the summary, a summary match above one in a section heading, and a heading match above one in the body, with an added score when every word of the query appears somewhere and a further one when the whole query appears in a title. Guides tied on score are ordered by slug, so the same query returns the same list in the same order on every call. No model runs and no network call is made. The limit parameter caps how many guides come back, from 1 to 10, default 5. An empty results array means no guide in this library contains any word of the query, which is a fact about the library and not about VA rules or about what VA holds. Reading one is a second call: pass a returned slug to get_guide. It reads no account data, so the answer is the same for every caller with the same inputs.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['query'], 'properties': {'limit': {'type': 'integer', 'maximum': 10, 'minimum': 1, 'description': 'How many guides to return, 1 to 10. Default 5.'}, 'query': {'type': 'string', 'description': 'What the veteran is asking about, in keywords or a short phrase, for example "C&P exam" or "how do I get my military medical records".'}}}
search_legal_authority
Search case law and regulations
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.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'properties': {'limit': {'type': 'number', 'description': 'Max results (default 5, max 10).'}, 'query': {'type': 'string', 'description': '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.'}, 'citation': {'type': 'string', 'description': '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.'}, 'diagnosticCode': {'type': 'string', 'description': 'Filter by diagnostic code (e.g., "8100").'}}}
履歴
最近のツール変更
変更
search_guides
2026年9月29日3:00
変更
find_claim_help
2026年9月29日3:00
変更
find_secondary_conditions
2026年9月29日3:00
変更
calculate_rolling_window
2026年9月29日3:00
追加
get_guide
2026年9月27日2:51
追加
search_guides
2026年9月27日2:51
変更
prepare_cp_exam
2026年9月27日2:51
変更
check_presumptive_eligibility
2026年9月27日2:51
変更
find_secondary_conditions
2026年9月27日2:51
変更
compare_rating_criteria
2026年9月27日2:51
追加
find_claim_help
2026年9月17日7:58
追加
compute_retroactive_pay
2026年9月17日7:58
追加
lookup_compensation_rate
2026年9月17日7:58
追加
prepare_cp_exam
2026年9月17日7:58
追加
search_legal_authority
2026年9月17日7:58
追加
check_presumptive_eligibility
2026年9月17日7:58
追加
find_secondary_conditions
2026年9月17日7:58
追加
calculate_rolling_window
2026年9月17日7:58
追加
analyze_rating_gap
2026年9月17日7:58
追加
compare_rating_criteria
2026年9月17日7:58
追加
calculate_combined_rating
2026年9月17日7:58
関連MCP
類似のMCPサーバー
mcp
com.medigami/mcp
Analyzes medical bills and insurance denials, estimates healthcare costs, identifies assistance options, and supports appeals and…
Medicare Coverage
io.github.pipeworx-io/medicare-coverage
Provides structured Medicare coverage documents, policy timelines, utilization, enrollment, supplier, and payment-related data fr…
Fda Drug Competition
io.github.pipeworx-io/fda-drug-competition
Analyzes FDA Orange Book drug applications, patents, exclusivities, generic competition, and loss-of-exclusivity timelines.
FDA Data MCP
io.github.medley/fda-data
Searches and analyzes FDA data covering drugs, devices, facilities, inspections, recalls, approvals, shortages, enforcement, and …
Cms Open Payments
io.github.pipeworx-io/cms-open-payments
Searches and analyzes CMS Open Payments data on payments from pharmaceutical and device companies to physicians, hospitals, and o…
Dailymed
io.github.pipeworx-io/dailymed
Retrieves FDA DailyMed structured drug labels, label histories and diffs, drug classes, recent updates, and label references by d…
Codex Gsfa
io.github.pipeworx-io/codex-gsfa
Queries Codex GSFA food-additive regulations, including permitted additives, food categories, maximum use levels, qualifying note…
Sfda Drugs
io.github.pipeworx-io/sfda-drugs
Provides Saudi Food and Drug Authority drug records and related regulatory and market research access.