Skip to main content
Glama

labels

Manage global and personal tags: list available entries, create admin-defined global tags, and delete your own tags everywhere.

Instructions

List global labels and your own. create: add a global type: value (admin, only when asked). delete: remove one of your labels everywhere (global ones: admin).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
createNo
deleteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that creation is admin-gated and "only when asked" and that deletion propagates "everywhere," which is meaningful blast-radius context. It omits reversibility, whether deleting a global label affects other users, and what listing returns or how it is ordered.

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

Conciseness3/5

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

It is short with no filler, but the telegraphic colon-chained style ("create: add a global type: value") is grammatically broken and forces the agent to parse structure out of punctuation. Front-loading the list behavior is good; the mode documentation should be restructured rather than compressed further.

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 tool with a mutation surface (create/delete), zero annotations, and no output schema, the definition is thin. It never says what the listing returns, whether deletes are reversible, or how the three modes interact, leaving an agent to guess at the most consequential behavior.

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 description coverage is 0%, so the description must compensate; it does explain that `create` takes a "type: value" pair and that both operations are permission-gated. However, the "type: value" syntax is cryptic with no format example or valid type list, and `delete` is described only as "one of your labels" with no naming convention.

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 first clause states a specific verb and resource: "List global labels and your own." The following clauses disclose that the same tool also creates and deletes via optional parameters, which distinguishes it from the sibling `delete` tool only implicitly. An agent can tell what the tool does, but the multi-mode nature is compressed into shorthand rather than stated as modes.

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

Usage Guidelines3/5

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

It gives partial when-to guidance: create is admin-scoped and "only when asked," and delete removes a label "everywhere" with admin needed for global ones. There is no guidance on when to use this tool's delete mode versus the sibling `delete` tool, and no condition distinguishing listing global vs personal labels beyond the default.

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