Skip to main content
Glama
Sign In
huly-mcp-selfhost

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_label

Creates a workspace-wide label with an optional hex color and reuses an existing title instead of duplicating it. Use it to organize issues consistently.

Instructions

Create a workspace-wide label (optional hex color); an existing title is reused. Tag an issue: add_label

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": {
      "workspace": "<workspace>",
      "title": "<title>"
    },
    "name": "create_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoHex color, e.g. #FF6B6B
titleYesLabel name
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.6.2
    • addedInput schema / properties / title / description
      Added value: +"Label name"
  2. First observedv3.5.1

TDQS

A4/5.0
Behavior3/5

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

Annotations only supply title and destructiveHint=false, so the description carries the real load. It does add valuable behavior beyond annotations—upsert/dedupe semantics ("an existing title is reused")—but says nothing about return value, whether the reused label is returned or mutated, or any permission requirements for workspace-wide creation.

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 with the create semantics front-loaded and the sibling routing second; nothing redundant, and the telegraphic "Tag an issue: add_label" is still unambiguous.

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

Completeness4/5

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

For a simple three-parameter, no-output-schema tool, the definition covers what it does, dedupe behavior, and the main alternative. The remaining gap is what an agent gets back (new vs. existing label identity), which matters since a reused title means the create call may not produce a new entity.

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 67%, with the undocumented gap being `workspace`; "workspace-wide" hints at that scope but doesn't define the expected identifier or behavior when the workspace is wrong. "Optional hex color" corroborates the schema's color description rather than adding new meaning; the title parameter's reuse behavior is the one genuine addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create a workspace-wide label") and adds a distinguishing semantic: an existing title is reused. It also names the sibling to use for the tagging step (add_label), so it is separable from add_label/remove_label at a glance.

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

Usage Guidelines4/5

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

Explicitly routes the tagging case to add_label, which is the key ambiguity for a create_* tool sitting next to add_label. It does not state when-not to use it (e.g., when the label should be scoped to a single issue or team), but the primary alternative is named with its condition.

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

Deploy Server

Other Tools