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

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_labels

Read-only

Fetch every workspace-wide label to discover available tags for organizing Huly issues, epics, and projects.

Instructions

List all labels in the workspace

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

Input Schema

NameRequiredDescriptionDefault
workspaceNo
projectIdentifierNoIgnored (labels are workspace-wide)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe read, so the description carries less burden. It does add the workspace-wide scoping fact, which explains why labels can't be scoped elsewhere, but it says nothing about pagination, ordering, result volume, or whether archived/private labels are included.

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?

A single short sentence with zero filler, front-loading the verb and resource. Nothing redundant is included.

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 trivial read-only list tool with annotations covering safety and no output schema, the description is nearly adequate. But since workspace is not a required parameter yet labels are workspace-wide, an agent gets no explanation of what happens when workspace is omitted — a real gap for a tool this simple.

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 50%: projectIdentifier is documented as ignored (labels are workspace-wide), but the workspace parameter is undocumented in both schema and description. The phrase "in the workspace" loosely maps to it but adds no format, default, or optionality information beyond what the schema shows.

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 ("List all labels") plus scope ("in the workspace"), which is enough to distinguish it from add_label or bulk issue tools. It doesn't explicitly differentiate from the many other list_* siblings, but the resource noun does that work implicitly.

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 use this versus alternatives (e.g., fetching labels per-project or via issue details), no note that the list is unfiltered/unpaginated, and no mention of what an agent should do with the results. The only usage-relevant hint is buried in the schema, not the description.

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