R/IV — Verify Claims, Citations & Agent Actions

vendor.diligence

R/IV vendor.diligence — independent evidence-verification primitive for dependency risk. Completed paid execution returns an RVO plus signed R/IV Verification Receipt.

Input Schema

Name	Required	Description
`scope`	Yes
`vendor`	Yes
`question`	No
`request_id`	Yes	Caller-generated idempotency key for this paid execution attempt.
`public_urls`	No

Output Schema

Name	Required	Description
`cost`	Yes
`jobId`	Yes
`result`	Yes	R/IV Verification Object with evidence, limitations, verdict and resultHash.
`status`	Yes
`receipt`	Yes
`verdict`	Yes
`requestId`	Yes
`timestamps`	Yes
`operationId`	Yes
`schemaVersion`	Yes
`operationVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$id": "https://rdiv-production-runtime-production.up.railway.app/schemas/riv-machine-result-v2.json",
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "description": "Schema of a completed R/IV machine execution. Cryptographic receipt integrity does not independently establish the truth of any underlying conclusion. Free trials may use a separate contract.",
+  "properties": {
+    "cost": {
+      "additionalProperties": true,
+      "properties": {
+        "amount": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "currency": {
+          "const": "USD"
+        }
+      },
+      "required": [
+        "currency",
+        "amount"
+      ],
+      "type": "object"
+    },
+    "jobId": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "operationId": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "operationVersion": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "issuedAt": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "jobId": {
+          "type": "string"
+        },
+        "operationId": {
+          "type": "string"
+        },
+        "receiptId": {
+          "type": "string"
+        },
+        "receiptVersion": {
+          "type": "string"
+        },
+        "requestId": {
+          "type": "string"
+        },
+        "resultHash": {
+          "pattern": "^[a-f0-9]{64}$",
+          "type": "string"
+        },
+        "sha256": {
+          "pattern": "^[a-f0-9]{64}$",
+          "type": "string"
+        },
+        "signature": {
+          "pattern": "^[a-f0-9]{64}$",
+          "type": "string"
+        }
+      },
+      "required": [
+        "receiptVersion",
+        "receiptId",
+        "jobId",
+        "requestId",
+        "operationId",
+        "resultHash",
+        "issuedAt",
+        "sha256",
+        "signature"
+      ],
+      "type": "object"
+    },
+    "requestId": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "result": {
+      "additionalProperties": true,
+      "description": "R/IV Verification Object with evidence, limitations, verdict and resultHash.",
+      "properties": {
+        "limitations": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "operationId": {
+          "type": "string"
+        },
+        "resultHash": {
+          "pattern": "^[a-f0-9]{64}$",
+          "type": "string"
+        },
+        "verdict": {
+          "type": "string"
+        },
+        "verificationId": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "operationId",
+        "verificationId",
+        "verdict",
+        "limitations",
+        "resultHash"
+      ],
+      "type": "object"
+    },
+    "schemaVersion": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "status": {
+      "const": "COMPLETED"
+    },
+    "timestamps": {
+      "additionalProperties": true,
+      "properties": {
+        "completedAt": {
+          "format": "date-time",
+          "type": "string"
+        }
+      },
+      "required": [
+        "completedAt"
+      ],
+      "type": "object"
+    },
+    "verdict": {
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "requestId",
+    "jobId",
+    "operationId",
+    "operationVersion",
+    "status",
+    "verdict",
+    "result",
+    "receipt",
+    "cost",
+    "timestamps"
+  ],
+  "title": "R/IV Machine Verification Result v2 - authenticated paid execution",
+  "type": "object",
+  "x-riv-receipt-policy": {
+    "integrity": "server-side HMAC verification required for v1 receipts",
+    "meaning": "signed provenance and execution integrity; not evidence that an underlying claim is true"
+  },
+  "x-riv-status": "public-contract-v2-live-machine-completed-only"
+}

Changed3 schema fields changedOct 8, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties

Added value: +{
+  "public_urls": {
+    "items": {
+      "format": "uri",
+      "type": "string"
+    },
+    "maxItems": 100,
+    "type": "array"
+  },
+  "question": {
+    "maxLength": 10000,
+    "type": "string"
+  },
+  "request_id": {
+    "description": "Caller-generated idempotency key for this paid execution attempt.",
+    "maxLength": 200,
+    "minLength": 8,
+    "type": "string"
+  },
+  "scope": {
+    "maxLength": 20000,
+    "minLength": 3,
+    "type": "string"
+  },
+  "vendor": {
+    "maxLength": 1000,
+    "minLength": 1,
+    "type": "string"
+  }
+}

addedInput schema / required

Added value: +[
+  "vendor",
+  "scope",
+  "request_id"
+]

First observedOct 6, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It adds genuinely useful context that the tool is a 'paid execution' and that completion returns 'an RVO plus signed R/IV Verification Receipt,' which hints at cost and a verifiable output artifact. It still omits permission requirements, failure/refund behavior on unpaid attempts, and rate/limit characteristics.

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?

Two tight, front-loaded sentences with no padding; the core function is stated first and the return behavior second. The main weakness is that brevity comes at the cost of clarity due to unexplained acronyms rather than verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, 3-required tool with multiple near-identical siblings and an output schema, the description is too thin. It does not explain the required vendor/scope/question inputs or differentiate behavior from vendor.monitor/dependency.map, leaving substantial ambiguity despite the output schema covering return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only request_id is documented), so the description must compensate — but it says nothing about vendor, scope, question, or public_urls. The four undocumented parameters remain opaque, so the description does not fill the gap the schema leaves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the tool as an 'independent evidence-verification primitive for dependency risk,' which conveys a verification function on a vendor/dependency subject. However, it leans heavily on undefined jargon ('R/IV', 'RVO', 'Verification Receipt') and never distinguishes its purpose from close siblings like vendor.monitor or dependency.map, so the agent cannot cleanly tell what unique job this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as vendor.monitor, dependency.map, or procurement.evidence. The agent is left to infer the routing decision entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All R/IV — Verify Claims, Citations & Agent Actions tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?