Proof Holdings

get_2fa_status

Read-only

Check the status of a 2FA session by session ID. Returns whether the challenge has been completed, is pending, or has expired.

Agent usage: Poll this after calling start_2fa. Check every few seconds. Terminal states: "verified" (proceed with protected operation), "expired" (restart with start_2fa). While "pending", the user has not yet entered their code.

Before calling this for a challenge you created, make sure your reply text already shows the user what to act on — the link itself, the SMS text and number, or a note to check their inbox; a link that appeared only in a tool result is one they never saw.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), or sign in with start_login — a session opens this tool — then call this tool again.

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": {
      "session_id": "<session_id>"
    },
    "name": "get_2fa_status"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	2FA session ID

Output Schema

Name	Required	Description
`status`	Yes
`session_id`	Yes
`action_type`	Yes	The action the session was started for: one of `TwoFAActionType` for sessions started through this API; admin-console sessions carry internal values.
`verified_at`	No
`grant_expires_at`	No	When the grant this step-up stored stops being accepted
`grant_single_use`	No	Whether the grant is spent by the first act it allows

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 2FA session's state; the grant fields are present once `status` is `verified`",
+  "properties": {
+    "action_type": {
+      "description": "The action the session was started for: one of `TwoFAActionType` for sessions started through this API; admin-console sessions carry internal values.",
+      "type": "string"
+    },
+    "grant_expires_at": {
+      "description": "When the grant this step-up stored stops being accepted",
+      "type": "string"
+    },
+    "grant_single_use": {
+      "description": "Whether the grant is spent by the first act it allows",
+      "type": "boolean"
+    },
+    "session_id": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "verified_at": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "session_id",
+    "status",
+    "action_type"
+  ],
+  "type": "object"
+}

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

TDQS

A4.1/5.0

Behavior5/5

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

readOnlyHint already covers the safety profile, and the description adds real value on top: the state machine semantics, the polling cadence, the access requirement (Proof account, authenticate or start_login — unusual and non-obvious), and the critical constraint that user-facing text must contain the link/SMS/number before polling. That last item is a behavioral gotcha an agent could not infer from any structured field.

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?

Purpose is front-loaded in the first sentence, then a clearly labeled 'Agent usage:' block, then access. Every sentence carries information the agent needs to act; nothing is repeated from the schema or annotations.

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 annotations, an output schema, and full param coverage already present, the description fills the remaining gaps: lifecycle states, next actions, access/auth path. The only omission is not naming wait_for_2fa as the blocking alternative, which leaves the agent to guess between polling and waiting.

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?

Single parameter at 100% schema coverage, so the schema already defines session_id fully. The description only restates 'by session ID' and adds nothing about where the ID comes from or whether it is reusable across calls — 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+resource ('Check the status of a 2FA session by session ID') and enumerates the outcome states (completed/pending/expired), which is far beyond the bare name. It does not, however, distinguish itself from the close sibling wait_for_2fa, which is the obvious blocking alternative for the same resource.

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?

'Poll this after calling start_2fa. Check every few seconds' gives an explicit trigger and cadence, and the terminal-state mapping ('verified' → proceed, 'expired' → restart with start_2fa, 'pending' → user hasn't entered code) tells the agent exactly what to do next. It never says when NOT to use it or that wait_for_2fa exists as a blocking substitute.

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.