GENESIS ProofRelay MCP Verifier

Build closing proof pack

proofrelay.build_closing_proof_pack

Read-onlyIdempotent

Build a hash-only closing proof pack manifest from settlement, title, lender, funding, notary, disbursement, and approval hashes. The tool does not authorize closing or disbursement.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`closing_pack`	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: -{
-  "ClosingProofPackInput": {
-    "description": "Hash-only closing proof pack input.",
-    "properties": {
-      "approval_receipt_hashes": {
-        "description": "Human approval receipt hashes.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Approval Receipt Hashes",
-        "type": "array"
-      },
-      "closing_file_hash": {
-        "description": "SHA-256 closing file hash.",
-        "title": "Closing File Hash",
-        "type": "string"
-      },
-      "disbursement_hashes": {
-        "description": "Disbursement instruction hashes.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Disbursement Hashes",
-        "type": "array"
-      },
-      "funding_authorization_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional funding authorization hash.",
-        "title": "Funding Authorization Hash"
-      },
-      "lender_package_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional lender package hash.",
-        "title": "Lender Package Hash"
-      },
-      "non_secret_refs": {
-        "description": "Public-safe closing references.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Non Secret Refs",
-        "type": "array"
-      },
-      "notary_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional notary event hash.",
-        "title": "Notary Hash"
-      },
-      "settlement_statement_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional settlement statement hash.",
-        "title": "Settlement Statement Hash"
-      },
-      "title_policy_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional title policy hash.",
-        "title": "Title Policy Hash"
-      }
-    },
-    "required": [
-      "closing_file_hash"
-    ],
-    "title": "ClosingProofPackInput",
-    "type": "object"
-  }
-}

removedInput schema / properties / closing_pack / $ref
```
Removed value: -"#/$defs/ClosingProofPackInput"
```

addedInput schema / properties / closing_pack / properties

Added value: +{
+  "approval_receipt_hashes": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "closing_file_hash": {
+    "type": "string"
+  },
+  "disbursement_hashes": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "funding_authorization_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "lender_package_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "non_secret_refs": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "notary_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "settlement_statement_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "title_policy_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}

addedInput schema / properties / closing_pack / required
```
Added value: +[
+  "closing_file_hash"
+]
```
addedInput schema / properties / closing_pack / type
```
Added value: +"object"
```

removedInput schema / title

Removed value: -"build_closing_proof_packArguments"

First observedJun 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly and idempotent hints, which are consistent with the description's 'hash-only' and non-authorizing nature. The description adds valuable context by explicitly stating the tool does not authorize closing or disbursement, which is a behavioral constraint not conveyed by annotations alone. It also clarifies that the tool works only with hashes, not actual documents, providing extra transparency beyond structured fields.

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, tightly packed. The first sentence identifies the purpose and scope, and the second provides a critical caveat about what the tool does not do. Every word earns its place, and there is no redundant or filler language.

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

Completeness4/5

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

Given the tool's complexity (nested object with multiple optional fields) and the presence of an output schema (which likely describes the returned manifest), the description covers the essential inputs and the tool's non-authorizing behavior. It lists all hash categories and explicitly says it is hash-only. Minor omissions include the format of hash values and the meaning of non_secret_refs, but these are partially addressed by the schema and do not severely hinder correct invocation.

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

Parameters4/5

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

Though the schema description coverage is 0%, the description compensates by enumerating all the hash categories (settlement, title, lender, funding, notary, disbursement, approval) that correspond to the nested closing_pack fields. This gives semantic meaning beyond the bare schema definitions, though it doesn't explain non_secret_refs or the structure of closing_pack itself. Since the schema is rich and nested, the description's enumeration of hash types adds significant value.

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's purpose: to build a hash-only closing proof pack manifest from a specific set of hash categories (settlement, title, lender, funding, notary, disbursement, approval). It also explicitly notes what it does not do (authorize closing or disbursement), distinguishing it from potential sibling tools like build_audit_pack_manifest or build_bundle_draft.

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 description implies the tool is used when you need to assemble a closing proof pack from hashes, and it clarifies it does not authorize actions. However, it does not explicitly state when to use this tool versus alternatives like build_audit_pack_manifest or other build_* siblings, nor does it mention any prerequisites or exclusions beyond the authorization caveat.

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?