Skip to main content
Glama

delete_server

DestructiveIdempotent

Deletes a server only when allowDevDelete is enabled, moving its logs to trash so admins can restore or empty them.

Instructions

Deletes a server (off by default — works only when the user turns on allowDevDelete in the admin app settings). Logs move to the trash, where the admin app can restore or empty them.

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": {
      "serverId": "<serverId>"
    },
    "name": "delete_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYesServer ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds real value beyond that by disclosing that deletion is gated behind an admin setting and that logs are moved to the trash where they can be restored or emptied. It stops short of saying whether the server object itself is recoverable, which leaves an important destructive-behavior detail ambiguous.

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?

Two tight sentences, front-loaded with the action, then the gating condition, then the post-delete behavior. No filler or repeated information.

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 one-parameter destructive tool with annotations covering the safety profile and no output schema, the description supplies the two things an agent most needs: the feature-flag prerequisite and the trash/restore consequence. Nothing essential to calling it 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% for the single serverId parameter, so the schema already carries the meaning. The description adds no format, sourcing, or validation detail beyond what the schema provides, which is the expected baseline here.

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, 'Deletes a server,' which is immediately distinguishable from the sibling delete_channel by resource type. It also names the gating setting, so an agent knows this is a conditional destructive operation rather than a general-purpose one.

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

Usage Guidelines4/5

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

It states a concrete precondition: the tool is off by default and only works when the user enables allowDevDelete in the admin app settings. That is strong when-to-use context, but there is no explicit guidance about alternatives or what to do if the setting is disabled (e.g., fall back or surface an error).

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