Skip to main content
Glama
Sign In

Proof Holdings

by holdings.proof
OverviewDiscussionsAdmin

check_user_domain_verification

Trigger a check on the domain verification challenge. Call after placing DNS record or HTTP file.

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": "check_user_domain_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesDomain verification session ID

Output Schema

NameRequiredDescriptionDefault
assetNoThe domain asset holding the proof; present when `status` is `verified`
statusYes
messageNoWhy the check is still pending; present when `status` is `pending`
verified_atNoPresent when `status` is `verified`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "The result of one check of the published record or file",
+  "properties": {
+    "asset": {
+      "additionalProperties": {},
+      "description": "The domain asset holding the proof; present when `status` is `verified`",
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "identifier": {
+          "type": "string"
+        },
+        "proof_expires_at": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "type",
+        "identifier"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "description": "Why the check is still pending; present when `status` is `pending`",
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "verified_at": {
+      "description": "Present when `status` is `verified`",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description adds real context beyond annotations: it discloses the authentication prerequisite (Proof account, /mcp authenticate or start_login) and the two-step session flow where a session opens the tool and the call is then repeated. It doesn't explain whether the check is synchronous, whether it must be polled, or whether it can be re-triggered repeatedly, but the auth and sequencing details are substantive.

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?

The action and its precondition are front-loaded in the first sentence, with the access/auth block clearly separated below. The auth paragraph is somewhat verbose but each sentence serves a recovery path for an unauthenticated agent.

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?

An output schema exists, so return values need no explanation, and the auth path is fully described. The remaining gap is whether the agent should poll or re-invoke after the check, which matters for a verification-check tool but is not addressed.

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 session_id parameter, so the schema already carries the parameter documentation. The description alludes to a session being opened by the auth flow but adds no format or sourcing detail for session_id beyond that. 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: triggering a check on the domain verification challenge. However, it does not differentiate from the many near-identical siblings such as check_domain_verification, get_user_domain_verification_status, verify_domain, and start_user_domain_verification, leaving the agent to infer the distinction.

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?

"Call after placing DNS record or HTTP file" gives a concrete precondition for invocation, which is the key timing signal for this tool. It stops short of naming alternatives or when-not-to-use cases (e.g., when to use check_domain_verification or get_user_domain_verification_status instead).

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

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

Resources