covnmr_verify
Does this NMR data match this structure (smiles, required)? Returns a
verdict, the evidence it was read from, and per-atom assignments.
The data is ONE of: a spectrum file (`path`), a peak list (`peaks`, or its
JSON text `peaks_json`), or peak lists keyed by experiment (`experiments` /
`experiments_json`, e.g. {"1H": [...], "13C": [...]}). Absorbs the retired
covnmr_verify_peaks (the peak-list form) and the 1D form of covnmr_assign.
Multi-step: paste literature text into covnmr_parse_nmr_string first and
pass its `peaks` here.
READ `verdict` AND `evidence`, NOT `match_score`. `verdict` ("match" /
"possible match" / "inconclusive" / "no match") comes from decoy-calibrated
evidence (`evidence.z`, the share of the spectrum left unexplained, and
thresholds set on decoy structures in `evidence.verdict_calibration`).
`match_score` is coverage (`match_score_basis`) and decides nothing. A
structure with fewer predicted signals than any calibrated one gets
"inconclusive"; 19F and 31P have no error model, so on their own they are
always "inconclusive".
A peak list that declares its nucleus outranks `nucleus`; a list spanning
several nuclei is scored per nucleus (`per_nucleus`) and the combined
verdict is the most cautious of the nuclei that have an error model. 19F
and 31P are still scored but do not set that verdict
(`nuclei_not_in_verdict` says why). With `path` the file decides the
nucleus.
`peaks_json` may also be the whole answer of covnmr_parse_nmr_string
({"nucleus": ..., "peaks": [...]}); its nucleus counts as the list's own.
Combine 1H/13C with HRMS, from a file or a peak list: pass `hrms`, e.g.
{"formula": "C9H8O4", "mz": 181.0495, "adduct": "[M+H]+"}. The response
then lists each check in `evidence_checks` -- HRMS formula, HRMS mass
within `hrms_ppm_tolerance` ppm (default 10), the 1H integral sum against
the proton count, the 13C line count against the carbon count, and the
shifts -- and gives one answer in `verdict_combined`: a failed HRMS check
makes it "no match", a failed count check caps it at "inconclusive",
otherwise it is the shift verdict. `verdict` itself is unchanged. The count
checks run on a file too (from its integrals and picked lines).
Give `candidates` (up to 20 alternative SMILES) and `verdict_relative` says
whether this structure beats the best alternative. It may also say the
data cannot tell this structure from a regioisomer: then it is
"inconclusive" with `regioisomer_ambiguous: true`, and
`competing_candidate` names the regioisomer that is not ruled out. Omit
`tolerance_ppm` and the window follows the nucleus (1H 0.3 ppm, 13C 3.0).
For several spectra or 2D data of one compound use covnmr_sudoku.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "covnmr_verify"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hrms | No | ||
| path | No | ||
| peaks | No | ||
| smiles | No | ||
| api_key | No | ||
| nucleus | No | ||
| solvent | No | CDCl3 | |
| max_peaks | No | ||
| candidates | No | ||
| peaks_json | No | ||
| experiments | No | ||
| tolerance_ppm | No | ||
| max_unassigned | No | ||
| experiments_json | No | ||
| hrms_ppm_tolerance | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |