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.

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

Input Schema

Name	Required	Description	Default
`closing_pack`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 29, 2026

addedInput schema / properties / closing_pack / additionalProperties
```
Added value: +false
```
addedInput schema / properties / closing_pack / properties / approval_receipt_hashes / items / pattern
```
Added value: +"^\\s*(?:sha256:)?[0-9a-fA-F]{64}\\s*$"
```
addedInput schema / properties / closing_pack / properties / closing_file_hash / pattern
```
Added value: +"^\\s*(?:sha256:)?[0-9a-fA-F]{64}\\s*$"
```
addedInput schema / properties / closing_pack / properties / disbursement_hashes / items / pattern
```
Added value: +"^\\s*(?:sha256:)?[0-9a-fA-F]{64}\\s*$"
```

changedInput schema / properties / closing_pack / properties / funding_authorization_hash / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^\\s*(?:sha256:)?[0-9a-fA-F]{64}\\s*$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / closing_pack / properties / lender_package_hash / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^\\s*(?:sha256:)?[0-9a-fA-F]{64}\\s*$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / closing_pack / properties / notary_hash / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^\\s*(?:sha256:)?[0-9a-fA-F]{64}\\s*$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / closing_pack / properties / settlement_statement_hash / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^\\s*(?:sha256:)?[0-9a-fA-F]{64}\\s*$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / closing_pack / properties / title_policy_hash / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^\\s*(?:sha256:)?[0-9a-fA-F]{64}\\s*$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is largely covered. The description still adds genuine value by clarifying that only hashes are handled ("hash-only") and by explicitly disclaiming that building the pack authorizes closing or disbursement, which prevents an agent from treating it as a finalizing step. It does not cover validation behavior for malformed hashes.

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?

Two tight sentences with the capability first and the safety disclaimer second. No filler, no restatement of the title.

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?

An output schema exists, so return values need not be explained. Given a nested object with zero schema coverage, the description covers most of the substance (which hashes, absence of authorization semantics), though it would be stronger if it flagged the required field and the non-secret refs array.

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?

Schema description coverage is 0% and the single parameter is a nested object with eight sub-fields, so the schema alone leaves the agent guessing. The description names seven of the hash inputs, which maps well onto the sub-properties, but it omits the required closing_file_hash and non_secret_refs, and says nothing about which fields are nullable or that additional properties are rejected.

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?

States a specific verb and resource ("Build a hash-only closing proof pack manifest") and enumerates the hash sources it composes. That distinguishes it reasonably well, but it never names the closest sibling, build_audit_pack_manifest, so an agent must infer the boundary itself.

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 second sentence provides a negative scope boundary ("does not authorize closing or disbursement"), which is implicitly when-not guidance. However, there is no positive statement of the situation that should trigger this tool, no prerequisite that the referenced documents already exist, and no routing to build_audit_pack_manifest or build_human_approval_receipt as alternatives.

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?