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

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_channel

Creates a new Huly channel in a workspace, letting you set an optional topic and restrict access to invite-only members.

Instructions

Create a new channel

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>",
      "name": "<name>"
    },
    "name": "create_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
topicNoOptional channel topic/description
isPrivateNoInvite-only
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

D1.9/5.0
Behavior2/5

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

Annotations supply only destructiveHint=false and a title, leaving the description to explain mutation behavior — it does none of that. It does not say whether names must be unique within a workspace, what happens on a duplicate, whether the creator is auto-joined, or whether private channels require invites; the only claim (creation) does not contradict the annotations.

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

Conciseness2/5

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

It is short, but shortness here reflects under-specification rather than concision — a single four-word sentence with no front-loaded constraint, scope, or outcome.

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

Completeness1/5

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

For a mutation tool with four parameters, two of them required, half the schema undocumented, no output schema, and annotations covering only destructiveness, the description provides nothing an agent needs to invoke it safely or correctly.

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 50%: topic and isPrivate are documented in the schema, but name and the required workspace parameter are bare strings. The description adds zero parameter meaning, so the half of the schema that is undocumented stays unexplained.

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

Purpose2/5

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

"Create a new channel" restates the tool name create_channel almost verbatim, adding no scope, target, or distinguishing detail. It is not misleading, but an agent gains nothing beyond what the identifier already implies, and nothing separates it from the surrounding create_* siblings.

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 prerequisite (e.g., that a workspace is required), and no mention of alternatives such as invite/add-contact channels. Only the bare act of creation is implied.

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