Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Delete label

delete_label
DestructiveIdempotent

Permanently removes a label from a pod's catalog using its pod ID and label name. Use it to clean up unused labels, since deletion cannot be undone.

Instructions

Delete a label from the pod's catalog. 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": "<name>"
    },
    "name": "delete_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
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.1/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 openWorldHint=true, so the safety profile is covered structurally; 'This cannot be undone' merely reinforces it. The description adds scope ('the pod's catalog') but says nothing about side effects on messages or threads already carrying the label, nor about behavior when the label is absent.

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 and the destructive consequence immediately after. No redundant or filler wording.

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 simple two-parameter destructive operation whose annotations already flag danger and idempotency, the definition is nearly sufficient to invoke correctly. It is thin on the undocumented 'name' parameter and on what deletion means for existing label associations, which is the main open question for an agent.

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

Parameters2/5

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

Only pod_id is described (in the schema), leaving 'name' undocumented in both schema and description – the reader must infer it is the label name. The description contributes no clarification of either required parameter, so it does not compensate for the 50% coverage gap.

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?

States a specific verb and resource ('Delete a label') plus a scope ('from the pod's catalog'), which separates it from create_label and update_label without ambiguity. It stops short of explicitly contrasting with those siblings, but an agent cannot mistake what operation this performs.

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 to choose this over update_label or other delete_* siblings, and no stated prerequisites such as needing the label to exist or owning the pod. The only directional statement is the irreversibility warning, which is a consequence, not usage guidance.

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