Skip to main content
Glama

Delete device permanently

device_delete

Permanently delete a phone and wipe all of its saved data (apps, logins, files). Cannot be undone. Use device_terminate instead to stop it and keep the data. Requires confirm: true.

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": {
      "device_id": "<device_id>",
      "confirm": "<confirm>"
    },
    "name": "device_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the phone and its data are deleted for good
device_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses permanence, irreversible data loss across apps/logins/files, and the required confirmation. This is the critical behavioral context for a destructive tool.

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 four short, front-loaded sentences with no filler. Irreversibility and the alternative are surfaced immediately, which is appropriate for a destructive operation.

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?

For a simple two-parameter destructive tool with no output schema, the description supplies the essential safety, alternative, and confirmation context. The remaining gap is that it does not explain how to obtain or format device_id, but the core invocation context is otherwise complete.

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 50%. The confirm parameter is already documented in the schema as const true and described as required for permanent deletion, while device_id is not described in either place beyond the implication that it identifies the phone. The description reinforces the confirmation requirement but does not add meaningful device_id format or source guidance.

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 states a specific verb and resource: permanently delete a phone and wipe its saved data. It also explicitly distinguishes this tool from device_terminate, so an agent can tell the difference without inspecting schemas.

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 an explicit alternative: use device_terminate to stop the device while keeping data. That clearly identifies when to choose deletion versus termination, and it also notes the required confirm: true.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources