Skip to main content
Glama

delete_tool

Destructive

Permanently delete a custom HTTP tool by ID. Use when removing an unused tool definition.

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": {
      "id": "<id>"
    },
    "name": "delete_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

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 readOnlyHint=false, so the danger profile is known. The description still adds meaningful context by stating deletion is permanent, signaling irreversibility. It does not cover side effects such as breaking agents that reference the tool, or the behavior on an unknown ID.

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 short sentences with the action and the 'Permanently' qualifier front-loaded. Every word carries weight and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive tool, the definition covers action, permanence, and a basic use case. It leaves out what happens when the tool is in use by agents or when the ID doesn't exist, and there is no output schema to explain error or success responses.

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?

With only one parameter at 0% schema coverage, the description contributes the phrase 'by ID', indicating the identifier selects the tool. It adds no format, source, or validation detail beyond that, leaving the schema's bare string undocumented in both places.

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?

The description names a specific verb and resource ('Permanently delete a custom HTTP tool by ID'), making the operation distinguishable from create_tool, get_tool, and update_tool. It clarifies scope ('custom HTTP tool') but does not explicitly contrast with siblings.

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?

'Use when removing an unused tool definition' gives a when-to-use condition, which is more than nothing. However, it offers no exclusions or alternatives — e.g., that update_tool should be used to modify rather than delete, or what to do if the tool is still referenced elsewhere.

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