Proof Holdings

get_confirmation

Read-only

Get a confirmation by ID. Returns the full confirmation including status, response, and proof token.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.

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": {
      "id": "<id>"
    },
    "name": "get_confirmation"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Confirmation ID

Output Schema

Name	Required	Description
`id`	Yes	MongoDB ObjectId
`status`	Yes	Status of a confirmation request. A confirmation that times out is `denied`, with `response.channel` `system` and `response.text` `timeout`.
`hitl_id`	Yes
`message`	Yes	The stored ciphertext envelope, echoed back verbatim. The server never sees the plaintext, so this is never the human sentence — the approver decrypts it in their browser.
`resends`	No	Every "Send again" (`POST /confirmations/{id}/resend`), oldest first, the last 50 kept. Absent from an API that predates it.
`response`	No	The decision and its evidence (null while pending)
`created_at`	Yes
`timeout_at`	No	When this confirmation will time out
`updated_at`	Yes
`proof_token`	No	Signed proof of the decision, approval or denial alike, naming who decided (`decided_by`, plus `authorization_id` for an approver); null while pending and for a system denial (`response.channel` is `system`)
`resolved_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "A HITL confirmation request",
+  "properties": {
+    "created_at": {
+      "type": "string"
+    },
+    "hitl_id": {
+      "allOf": [
+        {
+          "type": "string"
+        },
+        {}
+      ]
+    },
+    "id": {
+      "description": "MongoDB ObjectId",
+      "type": "string"
+    },
+    "message": {
+      "description": "The stored ciphertext envelope, echoed back verbatim. The server never sees the plaintext, so this is never the human sentence — the approver decrypts it in their browser.",
+      "type": "string"
+    },
+    "proof_token": {
+      "description": "Signed proof of the decision, approval or denial alike, naming who decided (`decided_by`, plus `authorization_id` for an approver); null while pending and for a system denial (`response.channel` is `system`)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resends": {
+      "description": "Every \"Send again\" (`POST /confirmations/{id}/resend`), oldest first, the last 50 kept. Absent from an API that predates it.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "actor": {
+            "additionalProperties": {},
+            "properties": {
+              "api_key_id": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "kind": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "api_key_id"
+            ],
+            "type": "object"
+          },
+          "at": {
+            "type": "string"
+          },
+          "channels": {
+            "items": {
+              "additionalProperties": {},
+              "properties": {
+                "recipient": {
+                  "type": "string"
+                },
+                "type": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type",
+                "recipient"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "at",
+          "actor",
+          "channels"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "resolved_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "response": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "action": {
+              "type": "string"
+            },
+            "at": {
+              "type": "string"
+            },
+            "authorization_id": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "channel": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "decided_by": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "kid": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "public_key": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "signature": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "signed_input": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "text": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "action",
+            "at"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The decision and its evidence (null while pending)"
+    },
+    "status": {
+      "description": "Status of a confirmation request. A confirmation that times out is `denied`, with `response.channel` `system` and `response.text` `timeout`.",
+      "type": "string"
+    },
+    "timeout_at": {
+      "description": "When this confirmation will time out",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updated_at": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "hitl_id",
+    "message",
+    "status",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedSep 19, 2026

TDQS

A3.9/5.0

Behavior4/5

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

readOnlyHint=true is consistent with a "get" tool, and the description adds context annotations cannot carry: account-type requirement, the exact auth step needed before calling, and the fact that other tools (start_login) will not satisfy it. It does not say what happens if the ID is unknown or whether a pending confirmation is a valid input — minor remaining gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short blocks, front-loaded with purpose then the access constraint; every sentence carries information an agent needs. Slightly verbose in the parenthetical auth instructions, but not wasteful.

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 present, return values need not be described, and the read-only annotation covers safety. Combined with the auth prerequisite, an agent has what it needs to call this correctly; only error/not-found behavior is left unstated.

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 coverage is 100% for the single `id` parameter, so the schema already defines it. The description's "by ID" adds nothing about format or source of the ID (e.g., from create_confirmation or list_confirmations), so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ("Get a confirmation by ID") and names the payload contents. It is clearly distinct from list_confirmations by the "by ID" scoping, but it never explicitly names the nearest alternatives such as wait_for_confirmation or get_confirmation_approval_link.

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 ACCESS paragraph gives a concrete prerequisite (Proof account, authenticate via /mcp) and an explicit negative ("start_login does NOT open this tool"), which prevents a common wrong path. It stops short of saying when to prefer this read over wait_for_confirmation when a confirmation is still pending.

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

All Proof Holdings 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.