Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Update label

update_label
Idempotent

Rename or recolor an existing label in a pod's catalog to keep label names and colors organized.

Instructions

Rename or recolor a label in the pod's catalog.

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": "update_label"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds only the vague phrase "in the pod's catalog" and says nothing about partial-update semantics, whether an omitted color preserves the existing one, what happens on a name collision, or how the required 'name' relates to the optional 'new_name'.

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

Conciseness4/5

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

A single short sentence with the operation front-loaded and zero filler. It is efficient, though the brevity is achieved by omitting information rather than by tight editing, which is penalized in other dimensions.

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

Completeness2/5

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

For a four-parameter mutation tool with only 25% schema coverage and no output schema, the description is too thin. The name/new_name ambiguity and the lack of any statement about update scope or failure conditions leave real gaps an agent would need to resolve before calling it.

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?

Schema description coverage is only 25%, so the description needs to compensate, and it does so only partially: "rename" and "recolor" loosely map to new_name and color. It never explains the critical distinction between the required 'name' and the optional 'new_name', nor the meaning of the color value, leaving the most error-prone parameter relationship unresolved.

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 gives a specific verb pair ("Rename or recolor") and a specific resource ("a label") scoped to "the pod's catalog," which is enough to separate it from create_label and delete_label. It stops short of a full differentiation statement, but the operation is unmistakable.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no explicit routing to siblings such as create_label or delete_label. The only cue is the implied 'use this to change a name or color,' which an agent must infer from the verb.

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