GENESIS ProofRelay MCP Verifier

Build human approval receipt draft

proofrelay.build_human_approval_receipt

Read-onlyIdempotent

Build an unsigned, hash-only human approval receipt draft for authority, policy, and subject evidence. The tool does not create approval authority or certify the approver's identity.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`approval`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 21, 2026

removedInput schema / $defs

Removed value: -{
-  "HumanApprovalReceiptInput": {
-    "description": "Hash-only human approval receipt draft input.",
-    "properties": {
-      "approval_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional approval id.",
-        "title": "Approval Id"
-      },
-      "approved_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional ISO-8601 time.",
-        "title": "Approved At"
-      },
-      "approver_hash": {
-        "description": "SHA-256 hash of approver identity.",
-        "title": "Approver Hash",
-        "type": "string"
-      },
-      "approver_role": {
-        "description": "Public-safe approver role.",
-        "title": "Approver Role",
-        "type": "string"
-      },
-      "decision": {
-        "description": "Approval decision.",
-        "enum": [
-          "approved",
-          "rejected",
-          "needs_changes"
-        ],
-        "title": "Decision",
-        "type": "string"
-      },
-      "expires_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional ISO-8601 expiry.",
-        "title": "Expires At"
-      },
-      "non_secret_refs": {
-        "description": "Non-secret evidence references.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Non Secret Refs",
-        "type": "array"
-      },
-      "policy_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional policy hash.",
-        "title": "Policy Hash"
-      },
-      "reason_codes": {
-        "description": "Public-safe approval reason codes.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Reason Codes",
-        "type": "array"
-      },
-      "scope_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional scope hash.",
-        "title": "Scope Hash"
-      },
-      "subject_hash": {
-        "description": "SHA-256 hash of approved subject.",
-        "title": "Subject Hash",
-        "type": "string"
-      }
-    },
-    "required": [
-      "approver_role",
-      "approver_hash",
-      "decision",
-      "subject_hash"
-    ],
-    "title": "HumanApprovalReceiptInput",
-    "type": "object"
-  }
-}

removedInput schema / properties / approval / $ref

Removed value: -"#/$defs/HumanApprovalReceiptInput"

addedInput schema / properties / approval / properties

Added value: +{
+  "approval_id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "approved_at": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "approver_hash": {
+    "type": "string"
+  },
+  "approver_role": {
+    "type": "string"
+  },
+  "decision": {
+    "enum": [
+      "approved",
+      "rejected",
+      "needs_changes"
+    ],
+    "type": "string"
+  },
+  "expires_at": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "non_secret_refs": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "policy_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "reason_codes": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "scope_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "subject_hash": {
+    "type": "string"
+  }
+}

addedInput schema / properties / approval / required

Added value: +[
+  "approver_role",
+  "approver_hash",
+  "decision",
+  "subject_hash"
+]

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

removedInput schema / title

Removed value: -"build_human_approval_receiptArguments"

First observedJun 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description discloses that the receipt is unsigned and hash-only, and explicitly states it does not create authority or certify identity, adding behavioral context beyond the readOnlyHint and idempotentHint annotations. It doesn't contradict any annotations.

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 concise with two informative sentences, front-loading the purpose and adding a clarifying limitation without waste.

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

Completeness3/5

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

For a tool with a nested approval object and output schema, the description covers the purpose and limitations but does not explain how to structure the approval parameter or what the output contains. It is somewhat incomplete for a complex tool, but adequate given the output schema exists.

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

Parameters3/5

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

The description gives a high-level hint that the approval object contains authority, policy, and subject evidence, but does not explain the specific fields or their semantics. With 0% schema coverage, it partially compensates but lacks detail on the approval object structure.

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

Purpose5/5

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

The description clearly states the tool builds an unsigned, hash-only human approval receipt draft, specifying the resource and scope. It also distinguishes itself from sibling tools by emphasizing it does not create approval authority or certify identity.

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

Usage Guidelines4/5

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

The description gives clear context that this tool only drafts an unsigned receipt and does not create approval authority or certify identity, providing negative use cases. However, it doesn't explicitly mention alternative tools or positive when-to-use scenarios.

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?