Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Delete pod

delete_pod
DestructiveIdempotent

Permanently delete a pod by its pod_id; this action cannot be undone and only works for pods within the API key's scope.

Instructions

Delete a pod. This cannot be undone.

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": {
      "pod_id": "<pod_id>"
    },
    "name": "delete_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
pod_idYesA pod id the key can reach. The server rejects any id outside this key's scope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely covered. The description adds one genuinely useful piece of extra context — irreversibility ("This cannot be undone") — but says nothing about what happens to a pod's contents or to repeated calls on an already-deleted pod.

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, action first, consequence second, with zero filler. Every word earns its place.

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 with full schema coverage and rich annotations, the definition is minimally adequate. It omits side effects (what happens to the pod's messages or dependent resources) and the idempotent behavior that annotations imply but do not illustrate, which an agent deciding whether to call it would want.

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% and the pod_id description already explains the key-scope restriction the server enforces. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 uses a specific verb and resource ("Delete a pod"), which is immediately distinguishable from the sibling read/write operations (get_pod, create_pod). It stops short of explicitly contrasting with any sibling, but the action is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when this tool should be chosen over alternatives, nor any prerequisites (e.g., whether the pod must be empty, whether dependent messages survive). The only qualifier is the irreversibility warning, which is a caution rather than usage guidance.

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