Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Create label

create_label

Adds a named label to a pod's catalog so email threads can be categorized and filtered.

Instructions

Create 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": "create_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNo
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

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the mutation/safety profile is covered structurally. The description adds only the fact that labels live in a pod's catalog; it says nothing about duplicate-name behavior, whether creation fails on an existing name, or what a successful call returns.

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 front-loaded sentence with zero filler, which is structurally clean. The terseness is a symptom of missing content rather than wordiness, and the phrase "in the pod's catalog" does earn its place by establishing scope.

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 non-idempotent, open-world mutation tool with no output schema and two undocumented parameters, one sentence is far too thin. An agent cannot determine from this definition what a label is, whether names must be unique, what color format is accepted, or what happens on conflict.

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 33%: pod_id is documented in the schema, but name and color carry no descriptions anywhere. The description does not compensate at all — it never states that name is the label's display name or that color is expected as a hex string, leaving two of three parameters semantically opaque.

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 names a specific verb and resource ("Create a label") and scopes it to "the pod's catalog," which is more informative than the bare title. It is clearly distinguishable from the delete_label/update_label siblings by verb alone, but it never explains how it differs from other create_* tools or what a label conceptually is.

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 guidance, no prerequisites, and no mention of alternatives such as update_label for existing labels or list_labels for discovery. The agent must infer entirely from the verb that this is the tool for adding a new label.

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