jev_verify
Verify up to 100 claims against one evidence source, returning supported, contradicted or not_addressed with calibrated confidence before you assert them.
Instructions
Check up to 100 claims against one body of evidence: supported / contradicted / not_addressed per claim, with a calibrated confidence.
Pass evidence_path for anything you have not already read — do NOT read a file in order to pass its text. The server reads it, chunks it if it is large, checks every claim against every chunk and returns line ranges. Use evidence only for text you already hold.
Use it before you assert something to the user or write it into a file: hold your draft's claims to the source, or check a summary against the document it summarises.
The rubric is strictly literal and closed-world: supported only if the evidence states or entails it. A claim that is true in the world but absent from the evidence comes back not_addressed — which is the answer you want when hunting unsupported assertions. conflicting means one part of the evidence firmly supports it and another firmly contradicts it.
Claims should be single, self-contained statements — split compound sentences and resolve pronouns first.
all_supported is true only when every claim is supported AND the model was confident about each; treat review/escalate gates as claims a human should look at.
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": {
"claims": "<claims>"
},
"name": "jev_verify"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| claims | Yes | Self-contained statements to check, one per entry. Split compound claims. | |
| end_line | No | With `evidence_path`: last line to use, 1-based inclusive. Default end of file. | |
| evidence | No | Text you already hold. The only material the claims are judged against. | |
| start_line | No | With `evidence_path`: first line to use, 1-based inclusive. Default 1. | |
| thresholds | No | Override the server's configured gating thresholds for this call only. | |
| evidence_path | No | A file for the server to read, relative to the project root. Preferred over pasting file text. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| model | Yes | The versioned model id that actually answered. | |
| usage | Yes | Token usage. Jev charges for input tokens only. | |
| claims | Yes | One result per input claim, in input order. | |
| summary | Yes | Counts across all claims. | |
| latency_ms | Yes | Wall-clock time for the underlying API call(s), including retries. | |
| thresholds | Yes | ||
| est_cost_usd | No | Present for file evidence: estimated input-token cost of this call. | |
| all_supported | Yes | True only if every claim is `supported` and every gate is `auto`. | |
| evidence_path | No | Present when the evidence was read from a file; relative to the root. | |
| evidence_chunks | Yes | How many requests the evidence was split into. 1 unless it was large. |