Skip to main content
Glama

container_delete

Destructive

Delete a container. It must be emptied first, because deleting one deletes its stored files. External sources are not containers and cannot be deleted here.

Instructions

Delete a container. It must be emptied first, because deleting one deletes its stored files. External sources are not containers and cannot be deleted here. If your token asks before deleting, nothing is deleted yet: the call returns a deletion batch that Connapse carries out itself once your owner approves it. Read the outcome with deletion_status; don't repeat the call.

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": {
      "containerId": "<containerId>"
    },
    "name": "container_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
containerIdYesContainer ID or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations supply only destructiveHint=true; the description adds the consequential detail that deleting a container deletes its stored files and that emptying first is required. It also discloses the approval-gated behavior — the call returns a deletion batch rather than performing the deletion immediately — and warns against repeating the call, which is critical idempotency information an agent would otherwise get wrong.

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?

Front-loaded with the action, then preconditions, scope exclusions, and async behavior in a logical order. Every clause carries operational weight — the emptying rule, the external-source exclusion, the approval flow, and the don't-repeat warning — with no filler.

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?

With no output schema, the description still explains what comes back (a deletion batch carried out after owner approval) and how to check the result (deletion_status). For a single-parameter destructive tool, an agent has everything needed to call it correctly and interpret the response.

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% with a single documented containerId ("Container ID or name"), so the schema already carries parameter meaning. The description refers only to "a container" and adds nothing about the ID/name forms beyond what the schema states, making the baseline 3 appropriate.

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 first sentence names a specific verb and resource ("Delete a container"), and the following sentences bound the scope by excluding external sources and requiring the container be emptied first. An agent can tell this apart from delete_file and the container_* siblings without inspecting any schema.

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?

Explicit preconditions ("must be emptied first"), explicit exclusions ("External sources are not containers and cannot be deleted here"), and an explicit follow-up path ("Read the outcome with deletion_status; don't repeat the call"). Both when-to-use and when-not-to-use are stated, along with the alternative for reading results.

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