PriorSeal

priorseal_get_evidence_bundle

Read-onlyIdempotent

Get a free x402 purchase handoff for the portable receipt evidence bundle. This MCP result never includes the paid bundle itself.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "receiptId": "<receiptId>"
    },
    "name": "priorseal_get_evidence_bundle"
  }
}

Input Schema

Name	Required	Description	Default
`receiptId`	Yes	PriorSeal receipt identifier.

Output Schema

Name	Required	Description	Default
`data`	Yes
`risk`	Yes
`tool`	Yes
`schema`	Yes
`status`	Yes
`nextAction`	Yes
`requiresHumanSignature`	Yes
`mayBroadcastTransaction`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {},
+    "mayBroadcastTransaction": {
+      "const": false
+    },
+    "nextAction": {
+      "type": "string"
+    },
+    "requiresHumanSignature": {
+      "type": "boolean"
+    },
+    "risk": {
+      "additionalProperties": false,
+      "properties": {
+        "level": {
+          "enum": [
+            "read_only",
+            "human_signature_required",
+            "service_state_change",
+            "verification_only",
+            "input_or_service_error"
+          ]
+        },
+        "reasonCode": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "level",
+        "reasonCode"
+      ],
+      "type": "object"
+    },
+    "schema": {
+      "const": "priorseal.mcp.tool-result.v1"
+    },
+    "status": {
+      "type": "string"
+    },
+    "tool": {
+      "const": "priorseal_get_evidence_bundle"
+    }
+  },
+  "required": [
+    "schema",
+    "tool",
+    "status",
+    "nextAction",
+    "requiresHumanSignature",
+    "mayBroadcastTransaction",
+    "risk",
+    "data"
+  ],
+  "type": "object"
+}

First observedOct 18, 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 and closed-world, so the safety profile is covered. The description does add one genuinely non-obvious behavior — the result is free and never contains the paid bundle — but stops short of explaining the x402 purchase flow, what completing the handoff entails, or any cost/auth implications.

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 short sentences with zero padding, and the crucial caveat about the paid bundle is stated up front rather than buried.

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?

With an output schema, rich annotations, and a single fully documented parameter, the structured data carries most of the burden; the description supplies the one thing structured data cannot — that this is a handoff and not the deliverable itself. The remaining gap is workflow guidance for actually obtaining the paid bundle.

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?

One parameter with 100% schema description coverage, so the schema already defines receiptId as a 'PriorSeal receipt identifier'. The description adds nothing about where a receiptId comes from or what an invalid one does, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource is 'Get ... x402 purchase handoff for the portable receipt evidence bundle', which is specific but ambiguous about the object returned — is it the bundle or a handoff? The second sentence clarifies that it is a handoff, not the bundle itself. However, it never differentiates from the near-identically named sibling priorseal_get_evidence, so an agent cannot reliably choose between them.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternative. The closest thing to guidance is the implicit condition that you call this when you want the paid bundle but only get a purchase handoff, which the agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PriorSeal 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.