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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_domain

Destructive

Permanently remove a domain from your account, revoking its proofs and delegations and deleting its records; the response lists any remaining manual cleanup. Cannot be undone.

Instructions

Remove a domain from the account. Revokes every proof of the domain and every delegation issued from it (for good — re-adding the domain does not bring them back), deletes the domain and its records, and removes our _proof TXT record and the Resend sending domain where we can; the response lists what is left for you to remove by hand. Owner only, in a start_login session, with one code: start_2fa_for_action with action_type domain_remove and targets [this domain id]. Need only a fresh proof? Revoke the proofs instead (revoke_asset), which keeps the domain. Cannot be undone.

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, or sign in with start_login — a session opens this tool — then call this tool again.

Input Schema

NameRequiredDescriptionDefault
idYesDomain ID to delete

Output Schema

NameRequiredDescriptionDefault
domainNo
noticeNo
successNoAlways `true`. The 1.x Go, PHP and Python SDK types carry it as a string, as released; it is typed boolean in the next major.
carriersNoWhere the revoked delegations are still published (the `_mcp.<domain>` pointer, a delegate card) — bounded to a few delegations and a few seconds.
externalNo
proofs_revokedNo
delegations_revokedNo

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": {
+    "carriers": {
+      "description": "Where the revoked delegations are still published (the `_mcp.<domain>` pointer, a delegate card) — bounded to a few delegations and a few seconds."
+    },
+    "delegations_revoked": {},
+    "domain": {},
+    "external": {},
+    "notice": {},
+    "proofs_revoked": {},
+    "success": {
+      "description": "Always `true`. The 1.x Go, PHP and Python SDK types carry it as a string, as released; it is typed boolean in the next major."
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructive annotation, the description discloses the full cascade: proofs and delegations are permanently revoked, the domain and records are deleted, the _proof TXT record and Resend sending domain are removed where possible, and the response lists manual cleanup. It also states irreversibility and the exact authorization flow.

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?

The description is front-loaded with the action and consequences, then moves to the alternative, authorization requirements, and irreversibility. Every sentence carries operational value; none is filler.

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?

This is a destructive cascade tool with one parameter and an output schema. The description covers consequences, manual follow-up, authorization, alternative behavior, and irreversibility, so it is complete for correct selection and invocation.

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 description coverage is 100%, and the single id parameter is already documented as 'Domain ID to delete.' The description adds only that the id is the target of the 2FA action, without format or validation details. A baseline of 3 is appropriate when the schema carries parameter semantics.

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?

The description opens with a specific verb and resource: 'Remove a domain from the account.' It then distinguishes the operation from the narrower alternative by stating that revoke_asset should be used when only proofs need revoking. An agent can identify this as the destructive domain-removal tool without inspecting siblings.

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?

It gives explicit when-to-use and when-not-to-use guidance, including the alternative 'revoke_asset' for proof-only revocation. It also states prerequisites: owner only, start_login session, and start_2fa_for_action with action_type domain_remove and the domain id.

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