GENESIS ProofRelay MCP Verifier

Map OpenAPI operation evidence

proofrelay.map_openapi_operation_evidence

Read-onlyIdempotent

Map public OpenAPI operation metadata and schema hashes into a ProofRelay event plan with checkpoint recommendations for paid, mutating, or relied-upon API operations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operation`	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: -{
-  "OpenAPIOperationEvidenceInput": {
-    "description": "Public OpenAPI operation metadata mapped to ProofRelay evidence.",
-    "properties": {
-      "idempotency_required": {
-        "default": false,
-        "description": "True if the operation should require idempotency.",
-        "title": "Idempotency Required",
-        "type": "boolean"
-      },
-      "method": {
-        "description": "HTTP method for the operation.",
-        "enum": [
-          "GET",
-          "POST",
-          "PUT",
-          "PATCH",
-          "DELETE"
-        ],
-        "title": "Method",
-        "type": "string"
-      },
-      "operation_id": {
-        "description": "OpenAPI operationId or stable id.",
-        "title": "Operation Id",
-        "type": "string"
-      },
-      "path_template": {
-        "description": "Public path template, no secrets.",
-        "title": "Path Template",
-        "type": "string"
-      },
-      "payment_required": {
-        "default": false,
-        "description": "True if operation requires payment or entitlement.",
-        "title": "Payment Required",
-        "type": "boolean"
-      },
-      "request_schema_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional SHA-256 hash of the request schema.",
-        "title": "Request Schema Hash"
-      },
-      "response_schema_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional SHA-256 hash of the response schema.",
-        "title": "Response Schema Hash"
-      },
-      "security_scheme_refs": {
-        "description": "Non-secret names of OpenAPI security schemes used.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Security Scheme Refs",
-        "type": "array"
-      },
-      "server_url_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional SHA-256 hash of the server URL.",
-        "title": "Server Url Hash"
-      }
-    },
-    "required": [
-      "operation_id",
-      "method",
-      "path_template"
-    ],
-    "title": "OpenAPIOperationEvidenceInput",
-    "type": "object"
-  }
-}

removedInput schema / properties / operation / $ref

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

addedInput schema / properties / operation / properties

Added value: +{
+  "idempotency_required": {
+    "type": "boolean"
+  },
+  "method": {
+    "enum": [
+      "GET",
+      "POST",
+      "PUT",
+      "PATCH",
+      "DELETE"
+    ],
+    "type": "string"
+  },
+  "operation_id": {
+    "type": "string"
+  },
+  "path_template": {
+    "type": "string"
+  },
+  "payment_required": {
+    "type": "boolean"
+  },
+  "request_schema_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "response_schema_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "security_scheme_refs": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "server_url_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}

addedInput schema / properties / operation / required

Added value: +[
+  "operation_id",
+  "method",
+  "path_template"
+]

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

removedInput schema / title

Removed value: -"map_openapi_operation_evidenceArguments"

First observedJun 23, 2026

TDQS

A4/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. The description adds useful context by framing the tool as mapping metadata rather than invoking operations, and by highlighting paid, mutating, or relied-upon operations. It does not contradict annotations and provides enough behavioral context beyond the structured hints.

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, front-loaded sentence with no filler. It states the action, the input, and the output efficiently, making it easy for an agent to parse quickly.

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 tool has one nested parameter, an output schema, and annotations covering the safety profile, the description provides sufficient context for a mapping tool. It would benefit from explicit when-to-use guidance and a bit more parameter detail, but overall it is adequately complete.

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 adds high-level meaning by referencing 'schema hashes' and 'paid, mutating, or relied-upon' categories, which align with fields like payment_required, idempotency_required, and method. However, it does not explain individual nested fields such as operation_id, path_template, server_url_hash, or security_scheme_refs.

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 uses a specific verb ('Map') with a clear object ('public OpenAPI operation metadata and schema hashes') and a distinct output ('ProofRelay event plan with checkpoint recommendations'). It differentiates from siblings like wrap_mcp_tool_evidence by naming the OpenAPI source and the event-plan output.

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 description implies usage when public OpenAPI operation metadata is available and checkpoint recommendations are needed, but it does not explicitly state when to choose this over alternatives like map_lender_condition_evidence or wrap_mcp_tool_evidence. No exclusions or alternative tool references are provided.

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?