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

TableJSON Schema

Name	Required	Description	Default
`title_evidence`	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: -{
-  "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

A3.6/5.0

Behavior4/5

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

The description adds the information that it does not certify title status or legal sufficiency, which complements the annotations indicating read-only and idempotent behavior, though it does not detail all side effects.

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, concise and well-structured with no unnecessary information, clearly articulating the tool's core functionality and boundary.

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

Completeness2/5

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

The description lacks details on the output format, optional fields, and the meaning of production_status, making it incomplete for complex usage despite having an output schema.

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 mentions the types of hashes but does not explain individual fields such as non_secret_refs or production_status, leaving ambiguity for some parameters.

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 a hash-only title production evidence profile from specific hash types (order, property, title-search, commitment, exception, tax-cert), providing a specific verb and resource.

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 description does not specify when to use this tool versus alternatives, lacking explicit usage guidance or conditions for invocation.

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?