idempotency-fingerprint
Derive a stable idempotency fingerprint from declared identity fields and flag volatile fields — Hashes the fields you declare as the identity of an operation (JSON Pointers into each request) with RFC 8785 canonical JSON and SHA-256, so retries of the same operation get the same fingerprint regardless of key order, and flags the ways that breaks: an identity field missing, an identity field also declared volatile, identity values that look like timestamps, epoch times or UUIDs (heuristic), a
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": {
"requests": "<requests>",
"identity": "<identity>"
},
"name": "idempotency-fingerprint"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Mixed into the hash (for example operation name and tenant) so equal bodies in different scopes get different fingerprints. | |
| identity | Yes | JSON Pointers whose values define the operation's identity. | |
| requests | Yes | ||
| volatile | No | JSON Pointers declared to change per attempt (timestamps, nonces, request ids). |