Export the portable receipt evidence bundle and issuer key-discovery metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| receiptId | Yes | PriorSeal receipt identifier. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| risk | Yes | ||
| tool | Yes | ||
| schema | Yes | ||
| status | Yes | ||
| nextAction | Yes | ||
| requiresHumanSignature | Yes | ||
| mayBroadcastTransaction | Yes |
Changes observed during successful MCP inspections.
Output 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is fully covered structurally. The description adds the useful detail that the bundle is 'portable' and includes key-discovery metadata, but says nothing about size, format, or auth requirements for exporting.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; the resource and its companion metadata are stated up front. Nothing in the sentence is redundant with the name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described, and the parameter is fully specified. However, with nine sibling tools including several receipt-related ones, the absence of any routing guidance leaves a real gap in an otherwise simple definition.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single receiptId parameter is fully documented in the schema (100% coverage) as the 'PriorSeal receipt identifier'. The description adds no additional meaning about the identifier's format or provenance, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Export') and two concrete resources ('portable receipt evidence bundle', 'issuer key-discovery metadata'), which tells an agent what it gets back. It does not explicitly differentiate itself from close siblings such as priorseal_get_receipt or priorseal_verify_receipt, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool versus the other receipt-related siblings (get_receipt, verify_receipt), nor any prerequisites or exclusions. The agent must infer the selection criteria from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.