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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

preview_profile_deletion

Read-only

Preview the impact of deleting a sub-account without changing data: see dashboard counts, the replacement sub-account, or the refusal reason. Requires profiles:read.

Instructions

Preview what delete_sub_account would do to one sub-account, without changing anything: the counts the dashboard Delete sub-account dialog shows and the sub-account that would take its place, or why deletion is refused (allowed: false). Needs profiles:read; a key bound to a sub-account previews only its own.

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.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "preview_profile_deletion"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYesSub-account ID

Output Schema

NameRequiredDescriptionDefault
countsNo
allowedNo
blockedNo
projectNo
new_primaryNoNamed 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond readOnlyHint=true by disclosing the actual output shape (dashboard counts, the replacement sub-account, or a refusal with allowed: false) and the scoping rule for sub-account-bound keys. The ACCESS paragraph adds auth/setup context, though it reads as server-level boilerplate rather than tool-specific behavior.

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 functional sentence is front-loaded and dense with useful detail. The second ACCESS paragraph is generic setup text repeated across the server's tools, which slightly dilutes conciseness but is still actionable.

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?

With an output schema present, the description needn't enumerate return fields, yet it still summarizes the meaningful outcomes including the refusal case. Combined with permission and key-scoping notes, nothing an agent needs to call this 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% with a single documented profile_id, so the schema already carries the parameter meaning. The description adds only that the target is 'one sub-account' and that key binding constrains it, which is marginal beyond the schema baseline.

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 ('Preview what delete_sub_account would do to one sub-account') and explicitly frames it as a no-op dry run. The named sibling delete_sub_account makes the pairing unmistakable.

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?

Explicitly positions this as the safe preview step before delete_sub_account, and adds the conditions that govern use: profiles:read scope and the fact that a sub-account-bound key only previews its own sub-account. An agent knows both when to call it and what it will see.

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