GENESIS ProofRelay MCP Verifier

Generate paid tool receipt draft

proofrelay.generate_paid_tool_receipt

Read-onlyIdempotent

Generate an unsigned, hash-only paid MCP/API tool receipt draft that callers can include in a signed ProofRelay bundle. The tool does not charge, redeem, settle, or attest to external facts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`receipt`	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: -{
-  "PaidToolReceiptInput": {
-    "description": "Hash-only paid MCP/API tool receipt draft input.",
-    "properties": {
-      "authority_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional authority, policy, or scope hash.",
-        "title": "Authority Hash"
-      },
-      "entitlement_hash": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional public-safe entitlement hash.",
-        "title": "Entitlement Hash"
-      },
-      "non_secret_refs": {
-        "description": "Non-secret references to include.",
-        "items": {
-          "type": "string"
-        },
-        "title": "Non Secret Refs",
-        "type": "array"
-      },
-      "payment_context_hash": {
-        "description": "SHA-256 hash of normalized payment context.",
-        "title": "Payment Context Hash",
-        "type": "string"
-      },
-      "receipt_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Optional stable receipt id.",
-        "title": "Receipt Id"
-      },
-      "result_hash": {
-        "description": "SHA-256 hash of the tool result.",
-        "title": "Result Hash",
-        "type": "string"
-      },
-      "tool_call_hash": {
-        "description": "SHA-256 hash of the tool call.",
-        "title": "Tool Call Hash",
-        "type": "string"
-      },
-      "tool_name": {
-        "description": "Paid tool or API operation name.",
-        "title": "Tool Name",
-        "type": "string"
-      },
-      "ts_ms": {
-        "description": "Receipt timestamp in Unix milliseconds.",
-        "title": "Ts Ms",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "tool_name",
-      "ts_ms",
-      "tool_call_hash",
-      "result_hash",
-      "payment_context_hash"
-    ],
-    "title": "PaidToolReceiptInput",
-    "type": "object"
-  }
-}

removedInput schema / properties / receipt / $ref

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

addedInput schema / properties / receipt / properties

Added value: +{
+  "authority_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "entitlement_hash": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "non_secret_refs": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "payment_context_hash": {
+    "type": "string"
+  },
+  "receipt_id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "result_hash": {
+    "type": "string"
+  },
+  "tool_call_hash": {
+    "type": "string"
+  },
+  "tool_name": {
+    "type": "string"
+  },
+  "ts_ms": {
+    "type": "integer"
+  }
+}

addedInput schema / properties / receipt / required

Added value: +[
+  "tool_name",
+  "ts_ms",
+  "tool_call_hash",
+  "result_hash",
+  "payment_context_hash"
+]

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

removedInput schema / title

Removed value: -"generate_paid_tool_receiptArguments"

First observedJun 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by specifying 'unsigned, hash-only' and explicitly listing actions it does not perform (charge, redeem, settle, attest). This gives a clearer picture of side effects beyond safety hints. No contradiction with annotations observed.

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 extremely concise—two sentences—and the main action is stated in the first sentence. The second sentence adds necessary boundary conditions without redundancy. Every word earns its place, and the structure is front-loaded.

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?

Despite having an output schema, the tool has a complex nested input object that remains completely unexplained. The description does not mention the structure or required fields of the receipt parameter, nor any workflow context. Given the moderate complexity and the 0% parameter coverage, the description is insufficiently complete for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides zero explanation of the single 'receipt' parameter and its nested structure. Schema description coverage is 0%, and the description does not compensate by describing required fields like tool_name, ts_ms, or hashes. The agent receives no guidance on how to construct the receipt object, making parameter usage unclear.

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: to generate an unsigned, hash-only paid MCP/API tool receipt draft for inclusion in a signed ProofRelay bundle. The verb 'generate' and specific resource 'receipt draft' are unambiguous, and the 'does not charge, redeem, settle, or attest to external facts' line distinguishes it from other receipt or payment tools in the sibling set.

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 implies when to use the tool: when a caller needs a receipt draft for a paid tool call to include in a ProofRelay bundle. It also clarifies limitations ('does not charge, redeem, settle'), which implicitly warns against using it for those actions. However, it does not explicitly name alternative tools or provide when-not-to-use conditions, so it falls short of a full 5.

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?