GENESIS ProofRelay MCP Verifier

Build title production evidence

proofrelay.build_title_production_evidence

Read-onlyIdempotent

Build a hash-only title production evidence profile from order, property, title-search, commitment, exception, and tax-cert hashes. The tool does not certify title status or legal sufficiency.

Input Schema

Name	Required	Description	Default
`title_evidence`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 29, 2026

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

changedInput schema / properties / title_evidence / properties / tax_cert_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 / title_evidence / properties / title_commitment_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 / title_evidence / properties / title_search_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: -{
-  "TitleProductionEvidenceInput": {
-    "description": "Hash-only title production evidence profile input.",
-    "properties": {
-      "exception_hashes": {
-        "description": "Hashes of title exceptions.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Exception Hashes",
-        "type": "array"
-      },
-      "non_secret_refs": {
-        "description": "Public-safe file or order refs.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Non Secret Refs",
-        "type": "array"
-      },
-      "order_hash": {
-        "description": "SHA-256 hash of title order.",
-        "title": "Order Hash",
-        "type": "string"
-      },
-      "production_status": {
-        "default": "review_required",
-        "description": "Declared public production status.",
-        "enum": [
-          "open",
-          "clear",
-          "exceptions",
-          "review_required"
-        ],
-        "title": "Production Status",
-        "type": "string"
-      },
-      "property_hash": {
-        "description": "SHA-256 hash of property ref.",
-        "title": "Property Hash",
-        "type": "string"
-      },
-      "tax_cert_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional tax cert hash.",
-        "title": "Tax Cert Hash"
-      },
-      "title_commitment_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional title commitment hash.",
-        "title": "Title Commitment Hash"
-      },
-      "title_search_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional title search artifact hash.",
-        "title": "Title Search Hash"
-      }
-    },
-    "required": [
-      "order_hash",
-      "property_hash"
-    ],
-    "title": "TitleProductionEvidenceInput",
-    "type": "object"
-  }
-}

removedInput schema / properties / title_evidence / $ref

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

addedInput schema / properties / title_evidence / properties

Added value: +{
+  "exception_hashes": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "non_secret_refs": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "order_hash": {
+    "type": "string"
+  },
+  "production_status": {
+    "enum": [
+      "open",
+      "clear",
+      "exceptions",
+      "review_required"
+    ],
+    "type": "string"
+  },
+  "property_hash": {
+    "type": "string"
+  },
+  "tax_cert_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "title_commitment_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "title_search_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}

addedInput schema / properties / title_evidence / required
```
Added value: +[
+  "order_hash",
+  "property_hash"
+]
```
addedInput schema / properties / title_evidence / type
```
Added value: +"object"
```

removedInput schema / title

Removed value: -"build_title_production_evidenceArguments"

First observedJun 23, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds two useful caveats beyond that: the output is "hash-only" (no raw or secret data) and it is explicitly non-certifying for title status or legal sufficiency. It says nothing about whether the profile is persisted, what fields the resulting profile carries, or any size/rate constraints.

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 sentences, front-loaded with the action and inputs, followed by the one disqualifying caveat. No filler and nothing repeated from the title.

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?

The presence of an output schema means return values needn't be explained, and the non-certification caveat covers the main misuse risk. But for a tool with a nested seven-field object at 0% schema coverage, the description leaves real gaps — notably the production_status enum and non_secret_refs — and gives no usage context.

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 schema is a nested object with seven fields, so the description must carry the burden. It does map six of them loosely by naming the hash types (order, property, title-search, commitment, exception, tax-cert), but leaves non_secret_refs and the production_status enum (open/clear/exceptions/review_required) completely unexplained, and gives no semantics for the required order_hash/property_hash beyond their names.

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 title production evidence profile") and enumerates the hash inputs it consumes, which distinguishes it from the verify_* and build_* proof-pack siblings reasonably well. It stops short of naming an explicit sibling it should not be confused with, but the resource is concrete enough to select on.

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

Usage Guidelines2/5

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

The only guidance is a scope exclusion ("does not certify title status or legal sufficiency") — a boundary, not a routing rule. There is no statement of when an agent should reach for this versus proofrelay.build_closing_proof_pack, proofrelay.map_lender_condition_evidence, or the verify tools, and no prerequisites are given.

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?