GENESIS ProofRelay MCP Verifier

Compute readiness signal

proofrelay.compute_readiness_signal

Read-onlyIdempotent

Compute a public-safe readiness signal from title, closing, wire, lender-condition, approval, exception, and risk hashes/counts. The tool does not certify readiness to close or fund.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`readiness`	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: -{
-  "ReadinessSignalInput": {
-    "description": "Hash-only real-estate workflow readiness signal input.",
-    "properties": {
-      "approval_receipt_hashes": {
-        "description": "Human approval receipt hashes.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Approval Receipt Hashes",
-        "type": "array"
-      },
-      "closing_pack_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Closing pack hash.",
-        "title": "Closing Pack Hash"
-      },
-      "critical_risk_count": {
-        "default": 0,
-        "description": "Critical risk count.",
-        "minimum": 0,
-        "title": "Critical Risk Count",
-        "type": "integer"
-      },
-      "lender_condition_hashes": {
-        "description": "Lender condition profile hashes.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Lender Condition Hashes",
-        "type": "array"
-      },
-      "open_condition_count": {
-        "default": 0,
-        "description": "Open condition count.",
-        "minimum": 0,
-        "title": "Open Condition Count",
-        "type": "integer"
-      },
-      "target_milestone": {
-        "description": "Milestone being assessed.",
-        "enum": [
-          "title_clear_to_close",
-          "closing",
-          "funding",
-          "disbursement",
-          "post_close"
-        ],
-        "title": "Target Milestone",
-        "type": "string"
-      },
-      "title_evidence_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Title evidence hash.",
-        "title": "Title Evidence Hash"
-      },
-      "unresolved_exception_count": {
-        "default": 0,
-        "description": "Public count of unresolved exceptions.",
-        "minimum": 0,
-        "title": "Unresolved Exception Count",
-        "type": "integer"
-      },
-      "wire_review_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Wire review hash.",
-        "title": "Wire Review Hash"
-      },
-      "workflow_hash": {
-        "description": "SHA-256 workflow or file hash.",
-        "title": "Workflow Hash",
-        "type": "string"
-      }
-    },
-    "required": [
-      "workflow_hash",
-      "target_milestone"
-    ],
-    "title": "ReadinessSignalInput",
-    "type": "object"
-  }
-}

removedInput schema / properties / readiness / $ref
```
Removed value: -"#/$defs/ReadinessSignalInput"
```

addedInput schema / properties / readiness / properties

Added value: +{
+  "approval_receipt_hashes": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "closing_pack_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "critical_risk_count": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "lender_condition_hashes": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "open_condition_count": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "target_milestone": {
+    "enum": [
+      "title_clear_to_close",
+      "closing",
+      "funding",
+      "disbursement",
+      "post_close"
+    ],
+    "type": "string"
+  },
+  "title_evidence_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "unresolved_exception_count": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "wire_review_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "workflow_hash": {
+    "type": "string"
+  }
+}

addedInput schema / properties / readiness / required

Added value: +[
+  "workflow_hash",
+  "target_milestone"
+]

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

removedInput schema / title

Removed value: -"compute_readiness_signalArguments"

First observedJun 23, 2026

TDQS

A4.1/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, covering safety and idempotency. The description adds value beyond these by clarifying that the output is 'public-safe' and explicitly stating it does not certify readiness, which provides additional behavioral context about the tool's limitations 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, front-loaded with the core purpose, and includes a succinct caveat. There is no fluff, and every word adds value. It is appropriately concise for the tool's complexity.

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?

Given the tool's complexity (a nested object with 10 properties and an output schema), the description is minimal. It covers the purpose and input categories but does not explain the nature of the computed 'readiness signal' (e.g., what it represents, its format, or how to interpret it). While the output schema exists, the description does not add enough context to make the tool fully self-contained.

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%, so the description must compensate. It does list high-level categories (title, closing, wire, etc.) that map to the nested object fields, but it does not explain individual parameter meanings or the structure of the required 'readiness' object. It provides some context but not enough detail to fully understand each field without relying on names and types.

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 verb 'Compute' and the resource 'a public-safe readiness signal', and lists the specific input categories (title, closing, wire, etc.). It also includes a scope limitation ('does not certify readiness to close or fund'), which helps differentiate it from potential certification tools. This is specific and not tautological.

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 provides a clear negative usage guideline by stating the tool does not certify readiness, which tells the agent when not to use it for certification. However, it does not explicitly name alternative tools for certification or provide a positive 'use when' scenario, so it lacks full alternative guidance.

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?