GENESIS ProofRelay MCP Verifier

Review wire/payoff change evidence

proofrelay.review_wire_payoff_change

Read-onlyIdempotent

Review hash-only wire, payoff, or disbursement change metadata for red flags and required controls without approving funds movement.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`wire_change`	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: -{
-  "WirePayoffChangeInput": {
-    "description": "Hash-only wire or payoff change evidence input.",
-    "properties": {
-      "approval_hashes": {
-        "description": "Approval or escalation hashes.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Approval Hashes",
-        "type": "array"
-      },
-      "callback_evidence_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional callback or out-of-band verification hash.",
-        "title": "Callback Evidence Hash"
-      },
-      "change_request_hash": {
-        "description": "SHA-256 change request hash.",
-        "title": "Change Request Hash",
-        "type": "string"
-      },
-      "change_type": {
-        "description": "Change category under review.",
-        "enum": [
-          "wire_instruction",
-          "payoff_statement",
-          "disbursement_instruction",
-          "other"
-        ],
-        "title": "Change Type",
-        "type": "string"
-      },
-      "new_instruction_hash": {
-        "description": "SHA-256 new instruction hash.",
-        "title": "New Instruction Hash",
-        "type": "string"
-      },
-      "observed_red_flags": {
-        "description": "Public-safe red flag reason codes.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Observed Red Flags",
-        "type": "array"
-      },
-      "original_instruction_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional original instruction hash.",
-        "title": "Original Instruction Hash"
-      },
-      "payoff_statement_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional payoff statement hash.",
-        "title": "Payoff Statement Hash"
-      },
-      "requester_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional requester hash.",
-        "title": "Requester Hash"
-      }
-    },
-    "required": [
-      "change_type",
-      "change_request_hash",
-      "new_instruction_hash"
-    ],
-    "title": "WirePayoffChangeInput",
-    "type": "object"
-  }
-}

removedInput schema / properties / wire_change / $ref
```
Removed value: -"#/$defs/WirePayoffChangeInput"
```

addedInput schema / properties / wire_change / properties

Added value: +{
+  "approval_hashes": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "callback_evidence_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "change_request_hash": {
+    "type": "string"
+  },
+  "change_type": {
+    "enum": [
+      "wire_instruction",
+      "payoff_statement",
+      "disbursement_instruction",
+      "other"
+    ],
+    "type": "string"
+  },
+  "new_instruction_hash": {
+    "type": "string"
+  },
+  "observed_red_flags": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "original_instruction_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "payoff_statement_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "requester_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}

addedInput schema / properties / wire_change / required

Added value: +[
+  "change_type",
+  "change_request_hash",
+  "new_instruction_hash"
+]

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

removedInput schema / title

Removed value: -"review_wire_payoff_changeArguments"

First observedJun 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds transparency by noting 'hash-only' (limiting to hashes) and 'without approving funds movement,' which aligns with readOnly and complements the annotations. It does not contradict annotations and provides extra context about the nature of the review.

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 a single, concise sentence that packs essential information without fluff. It is well-structured and directly states the action and scope.

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 complexity of the tool (an object parameter and likely analysis output), the description provides sufficient context for a user to understand the review's purpose and constraints. It implies what the review covers (red flags, required controls) but does not elaborate on return format, which is acceptable as an output schema exists.

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 adds some semantic context by mentioning 'wire, payoff, or disbursement change metadata,' which maps to the change_type field, and 'hash-only' clarifies the data format. However, it does not explain individual properties within the wire_change object, so the schema remains the primary source for parameter details.

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: reviewing hash-only wire, payoff, or disbursement change metadata for red flags and required controls. It distinguishes itself from sibling tools by focusing on wire/payoff changes and explicitly stating it does not approve funds movement.

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 implicitly guides usage by indicating it reviews changes and explicitly states 'without approving funds movement,' providing a clear when-not scenario. However, it does not explicitly mention alternatives or compare with sibling review tools, leaving some ambiguity.

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?