Skip to main content
Glama
Sign In
@proof-holdings/mcp-server

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_domain_verification

Destructive

Delete a pending, verifying, or failed domain verification attempt without revoking. Verified or re-verification-needed domains are refused; use delete_domain to revoke proofs and delegations.

Instructions

Delete a domain verification attempt that is not verified (pending, verifying or failed) — nothing is revoked. A verified domain, or one that needs re-verification, is refused with domain_verified: removing it revokes its proofs and every delegation issued from it, which is delete_domain in a start_login session (or the dashboard).

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

Input Schema

NameRequiredDescriptionDefault
idYesDomain verification ID (24 hex characters)

Output Schema

NameRequiredDescriptionDefault
idYesThe id of the deleted domain verification
deletedYesThe domain verification was deleted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "deleted": {
+      "const": true,
+      "description": "The domain verification was deleted",
+      "type": "boolean"
+    },
+    "id": {
+      "description": "The id of the deleted domain verification",
+      "type": "string"
+    }
+  },
+  "required": [
+    "deleted",
+    "id"
+  ],
+  "type": "object"
+}
  2. Addedv1.6.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well past the destructiveHint=true annotation by disclosing that nothing is actually revoked, naming the exact refusal signal (domain_verified), and describing the side effects that the alternative (delete_domain) would trigger — proofs and all delegations. Auth prerequisites (PROOF_API_KEY, server restart) are spelled out. Missing only from annotations' perspective: irreversibility of the delete and behavior on an unknown ID.

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?

Front-loaded with the action and its constraint, and the ACCESS block is clearly separated. However, the clause 'which is delete_domain in a start_login session (or the dashboard)' is dense and hard to parse on first read, costing some clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter delete tool with an output schema and covering annotations, the definition supplies the refusal path, side effects, the alternative tool, and the auth gate. Return values are handled by the output schema, so nothing an agent needs to call it correctly is missing.

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% (single 'id' with a 24-hex pattern), so the schema already carries the format constraint. The description only implies the ID identifies a verification attempt rather than a domain, which is marginal added meaning; baseline 3 applies when the schema does the heavy lifting.

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

Purpose5/5

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

States a specific verb and resource ('Delete a domain verification attempt') and immediately bounds the scope to non-verified attempts via the enumerated statuses pending/verifying/failed. It explicitly distinguishes itself from delete_domain, so an agent can choose between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both when-to-use and when-not: unverified attempts can be deleted, verified or re-verification-pending domains are refused with a named error (domain_verified), and the correct alternative (delete_domain) is named for that case. The ACCESS paragraph further states the tool is unavailable in a start_login session, which is an unusual but important exclusion.

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

Deploy Server

Other Tools