@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

delete_profile

Destructive

Permanently delete a sub-account and revoke its API keys; archive HITL setups, decline pending requests, remove templates, retire its username, and keep history unlinked. Cannot be undone.

Instructions

Delete a sub-account (profile). Revokes its API keys, archives the HITL setups and declines the pending requests created with its own keys, keeps its history but unlinks it, deletes its message templates, and retires its username for good. The last sub-account cannot be deleted; deleting the primary sub-account makes the oldest remaining one primary (the response names it). In a start_login session: one code first — start_2fa_for_action with action_type profile_delete and targets [this sub-account id]. With an API key alone only an EMPTY sub-account (no API keys, HITL setups or pending requests) can be deleted; anything else answers owner_session_required. archive_default_linked is deliberately not offered here: archiving or cancelling everything linked only by default is an irreversible fan-out, so archive each item explicitly instead. 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

Name	Required	Description	Default
`profile_id`	Yes	Profile ID

Output Schema

Name	Required	Description
`message`	No
`project`	No
`success`	No	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.
`new_primary`	No	Named when the deleted sub-account is (or was) the primary: the OLDEST remaining sub-account takes over, and messages sent without choosing a sub-account carry its name.
`was_primary`	No
`hitl_archived`	No
`hitl_detached`	No
`api_keys_revoked`	No
`circles_detached`	No
`domains_detached`	No
`username_retired`	No	The username is retired for good — it can never be claimed again, by anyone.
`requests_detached`	No
`templates_deleted`	No
`requests_cancelled`	No
`confirmations_denied`	No
`authorizations_revoked`	No
`verifications_detached`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.7.2Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "api_keys_revoked": {},
+    "authorizations_revoked": {},
+    "circles_detached": {},
+    "confirmations_denied": {},
+    "domains_detached": {},
+    "hitl_archived": {},
+    "hitl_detached": {},
+    "message": {},
+    "new_primary": {
+      "description": "Named when the deleted sub-account is (or was) the primary: the OLDEST remaining sub-account takes over, and messages sent without choosing a sub-account carry its name."
+    },
+    "project": {},
+    "requests_cancelled": {},
+    "requests_detached": {},
+    "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."
+    },
+    "templates_deleted": {},
+    "username_retired": {
+      "description": "The username is retired for good — it can never be claimed again, by anyone."
+    },
+    "verifications_detached": {},
+    "was_primary": {}
+  },
+  "type": "object"
+}

First observedv1.1.0Sep 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only say destructiveHint=true; the description goes well beyond by spelling out every side effect (what is revoked, archived, declined, unlinked, and what is permanently destroyed - templates and the username), that the operation is irreversible, and the side effect of promoting the oldest remaining sub-account to primary (with the response naming it). Auth paths are covered (PROOF_API_KEY, start_login session, API key with empty-account restriction). It stops short of describing the response body, but an output schema exists so that is largely covered.

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 consequences, then prerequisites, then auth. Dense but nearly every sentence carries operative information; the only mild redundancy is "Cannot be undone" at the end, which restates destructiveHint, and the access note is longer than strictly necessary.

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 but high-blast-radius destructive tool, the definition covers side effects, irreversibility, prerequisite 2FA, error conditions, primary reassignment behavior, and authentication options. With an output schema present and naming the new primary, the description need not enumerate return fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single profile_id parameter, so the baseline would be 3. The description adds genuine meaning beyond the schema by tying the id to a downstream flow: it must be passed as targets [this sub-account id] to start_2fa_for_action when deleting inside a start_login session, which the schema's bare "Profile ID" does not convey.

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?

Opens with a specific verb+resource: "Delete a sub-account (profile)." It immediately enumerates the concrete effects (revokes API keys, archives HITL setups, declines pending requests, deletes message templates, retires username), which clearly separates it from create_profile, update_profile, set_primary_profile, and delete_hitl among the many 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?

Gives explicit when-can/cannot rules: the last sub-account cannot be deleted, an API-key-only caller may delete only an EMPTY sub-account, and it names the exact error (owner_session_required). It also routes the agent to a specific prerequisite sibling (start_2fa_for_action with action_type profile_delete) and explicitly explains why an alternative option (archive_default_linked) is deliberately not offered, telling the agent to archive items individually instead.

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

Deploy Server