GENESIS ProofRelay MCP Verifier

Recommend next checkpoint

proofrelay.recommend_checkpoint

Read-onlyIdempotent

Choose the next public-safe GENESIS checkpoint for a paid, material, or relied-upon agent workflow. Submit normalized context only; the tool returns reason codes without protected routing internals.

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": {
      "workflow_context": "<workflow_context>"
    },
    "name": "proofrelay.recommend_checkpoint"
  }
}

Input Schema

Name	Required	Description	Default
`workflow_context`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedInput schema / properties / workflow_context / additionalProperties
```
Added value: +false
```

Changed6 schema fields changedAug 21, 2026

removedInput schema / $defs

Removed value: -{
-  "WorkflowContext": {
-    "description": "Public-safe workflow context for checkpoint recommendation.",
-    "properties": {
-      "action_class": {
-        "description": "Public-safe action category, such as paid_api_call, paid_mcp_call, material_action, artifact_delivery, or counterparty_handoff.",
-        "examples": [
-          "paid_mcp_call"
-        ],
-        "title": "Action Class",
-        "type": "string"
-      },
-      "action_receipt_present": {
-        "default": false,
-        "description": "True when a portable agent action receipt already exists.",
-        "title": "Action Receipt Present",
-        "type": "boolean"
-      },
-      "artifact_delivery_expected": {
-        "default": false,
-        "description": "True when the workflow delivers an artifact to another party.",
-        "title": "Artifact Delivery Expected",
-        "type": "boolean"
-      },
-      "authority_envelope_present": {
-        "description": "True when agent authority, policy, scope, limits, and TTL are recorded.",
-        "title": "Authority Envelope Present",
-        "type": "boolean"
-      },
-      "counterparty_reliance_expected": {
-        "description": "True when another party is expected to rely on the result.",
-        "title": "Counterparty Reliance Expected",
-        "type": "boolean"
-      },
-      "dispute_or_audit_plausible": {
-        "description": "True when refund, SLA, audit, or dispute replay may be needed.",
-        "title": "Dispute Or Audit Plausible",
-        "type": "boolean"
-      },
-      "dispute_replay_present": {
-        "default": false,
-        "description": "True when a replay package for audit or dispute already exists.",
-        "title": "Dispute Replay Present",
-        "type": "boolean"
-      },
-      "evidence_bundle_present": {
-        "description": "True when a non-confidential evidence bundle is available.",
-        "title": "Evidence Bundle Present",
-        "type": "boolean"
-      },
-      "payment_context_present": {
-        "description": "True when the workflow has a payment, entitlement, or charge context.",
-        "title": "Payment Context Present",
-        "type": "boolean"
-      },
-      "receiver_acknowledgement_present": {
-        "default": false,
-        "description": "True when the receiving party has accepted, replayed, or rejected.",
-        "title": "Receiver Acknowledgement Present",
-        "type": "boolean"
-      },
-      "reliance_tier": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional reliance tier: low, standard, high, regulated, or critical.",
-        "examples": [
-          "high"
-        ],
-        "title": "Reliance Tier"
-      },
-      "verification_result_present": {
-        "default": false,
-        "description": "True when a prior verifier result is already available.",
-        "title": "Verification Result Present",
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "action_class",
-      "payment_context_present",
-      "authority_envelope_present",
-      "evidence_bundle_present",
-      "counterparty_reliance_expected",
-      "dispute_or_audit_plausible"
-    ],
-    "title": "WorkflowContext",
-    "type": "object"
-  }
-}

removedInput schema / properties / workflow_context / $ref
```
Removed value: -"#/$defs/WorkflowContext"
```

addedInput schema / properties / workflow_context / properties

Added value: +{
+  "action_class": {
+    "type": "string"
+  },
+  "action_receipt_present": {
+    "type": "boolean"
+  },
+  "artifact_delivery_expected": {
+    "type": "boolean"
+  },
+  "authority_envelope_present": {
+    "type": "boolean"
+  },
+  "counterparty_reliance_expected": {
+    "type": "boolean"
+  },
+  "dispute_or_audit_plausible": {
+    "type": "boolean"
+  },
+  "dispute_replay_present": {
+    "type": "boolean"
+  },
+  "evidence_bundle_present": {
+    "type": "boolean"
+  },
+  "payment_context_present": {
+    "type": "boolean"
+  },
+  "receiver_acknowledgement_present": {
+    "type": "boolean"
+  },
+  "reliance_tier": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "verification_result_present": {
+    "type": "boolean"
+  }
+}

addedInput schema / properties / workflow_context / required

Added value: +[
+  "action_class",
+  "payment_context_present",
+  "authority_envelope_present",
+  "evidence_bundle_present",
+  "counterparty_reliance_expected",
+  "dispute_or_audit_plausible"
+]

addedInput schema / properties / workflow_context / type
```
Added value: +"object"
```

removedInput schema / title

Removed value: -"recommend_checkpointArguments"

First observedJun 23, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it says to submit 'normalized context only' and that the tool returns 'reason codes without protected routing internals,' which clarifies input privacy constraints and output nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no wasted language, and the core action is front-loaded. The privacy/output caveat is placed immediately after the purpose, making it easy for an agent to scan.

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?

Although an output schema exists and annotations cover safety, the description is too thin for a tool with a complex 12-field nested input. It does not define what a 'GENESIS checkpoint' is in actionable terms or explain the workflow_context fields, leaving an agent without enough information to construct a correct call.

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 0%, and the single parameter is a nested object with 12 fields that are undocumented in both the schema and the description. The description only says 'Submit normalized context only,' which does not explain what the nested fields mean or how they should be populated, so it fails to compensate for the coverage gap.

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

Purpose4/5

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

The description states a specific verb and resource: 'Choose the next ... checkpoint' for a defined class of agent workflows. It does not explicitly differentiate itself from sibling tools such as proofrelay.compute_readiness_signal or proofrelay.build_* tools, and the term 'GENESIS checkpoint' is not defined, leaving some ambiguity.

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

Usage Guidelines3/5

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

The phrase 'for a paid, material, or relied-upon agent workflow' gives implied usage context, but the description does not state when not to use the tool or name alternative tools for related decisions. Guidance is present but not explicit.

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

All GENESIS ProofRelay MCP Verifier tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?