Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-delete

Destructive

Delete an AI resource from your Dokploy instance by supplying its AI ID, removing it through the official API.

Instructions

POST /ai.delete

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": {
      "aiId": "<aiId>"
    },
    "name": "ai-delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
aiIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the risk profile is partly covered externally. The description adds nothing beyond that: it does not say whether deletion is permanent, whether dependent resources are cascaded, or what happens if the ID does not exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short, but only because it is under-specified rather than efficient. A route string is not a front-loaded explanation of what the tool does or when to use it.

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

Completeness1/5

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

For a destructive, open-world tool with an undocumented required parameter and no output schema, the definition provides essentially no information an agent needs. Everything about the operation must be reverse-engineered from the name and annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, aiId, with 0% schema description coverage, and the description supplies no meaning for it. It is unclear whether aiId is a name, numeric ID, UUID, or provider-scoped reference, leaving the caller unable to construct a valid call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"POST /ai.delete" merely restates the tool name and HTTP route; it never says what an 'ai' resource is or what deleting it removes. An agent can infer a destructive operation on an AI entity, but only by combining the name with the annotation.

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

Usage Guidelines1/5

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

No when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as ai-get, ai-update, or ai-create. The agent is left to guess whether this removes a model, a provider config, or an entire AI resource.

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