Proof Holdings

delete_template

Destructive

Delete a sub-account's custom template, reverting that sub-account to the default template for the channel and message type.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), 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": {
      "channel": "<channel>",
      "message_type": "<message_type>"
    },
    "name": "delete_template"
  }
}

Input Schema

Name	Required	Description
`channel`	Yes	Message channel
`profile_id`	No	The sub-account to act on; omitted → your key's sub-account, or the primary sub-account for an account-wide key
`message_type`	Yes	Message type (e.g. verification_request, login_request)

Output Schema

Name	Required	Description	Default
`message`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

changedInput schema / properties / profile_id / description

Previous value: -"The sub-account (project) to act on; omitted → your key's project, or the primary project for an account-wide key"New value: +"The sub-account to act on; omitted → your key's sub-account, or the primary sub-account for an account-wide key"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Generic success response",
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedOct 16, 2026

addedInput schema / properties / profile_id

Added value: +{
+  "description": "The sub-account (project) to act on; omitted → your key's project, or the primary project for an account-wide key",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}

First observedSep 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, and the description earns credit by disclosing the exact consequence beyond mere removal: the sub-account falls back to the default template for that channel and message type. It also usefully warns that start_login will not unlock this tool, preventing a common failed-auth loop. It does not say what happens if no custom template exists for that channel/message type.

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 core sentence is front-loaded and states purpose plus consequence without waste. The access paragraph is somewhat boilerplate-heavy but is actionable and clearly separated, so it earns its place.

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 not be explained, and annotations cover the destructiveness profile. Combined with the stated revert behavior and auth prerequisite, an agent has what it needs to invoke this correctly; only the no-existing-template edge case is unaddressed.

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%, including the profile_id default-resolution rule and the channel enum, so the schema carries the burden. The description only loosely reinforces channel/message_type via 'for the channel and message type'; it adds no format or edge-case semantics beyond that, making baseline 3 appropriate.

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 (delete), a specific resource (a sub-account's custom template), and the resulting state (revert to the default template for the channel/message type). An agent can tell this apart from update_template, get_template, and list_templates from the text alone, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

The intended use case is implied clearly by 'custom template' plus 'reverting to default', but there is no explicit when-to-use/when-not guidance and no routing to update_template (to modify) or delete_profile (to remove the sub-account entirely). The second paragraph gives authentication guidance, which is about access rather than tool selection.

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

All Proof Holdings tools Inspect

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.