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

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

start_direct_message

Opens or locates a 1:1 direct message chat with a specified person in a workspace.

Instructions

Start or find a 1:1 DM with a person

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

Input Schema

NameRequiredDescriptionDefault
memberYesPerson name
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false and a title; there is no readOnlyHint, so the agent cannot tell whether this creates state. The description does add real value by disclosing the find-or-create ('start or find') behavior, which is not in the annotations. It says nothing about permissions, whether a message is sent, or what happens when a name is ambiguous.

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 eight-word sentence with no filler and the key qualifier ('1:1') up front. Terseness here edges toward under-specification rather than waste, so it is efficient but thin.

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 two-parameter tool with no output schema, the description leaves meaningful gaps: the undocumented workspace parameter, what 'find' returns for an existing DM, and whether the caller must then send a message separately. Adequate to attempt a call, not complete enough to predict the outcome.

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% — member is documented as 'Person name' while workspace has no description anywhere. The description only reinforces that member is a single person ('1:1 ... with a person') and adds nothing about how workspace scopes the lookup or how name matching resolves.

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 pair and resource: 'Start or find a 1:1 DM with a person'. The '1:1' qualifier distinguishes it from channel creation and message sending without needing the schema. It does not name a sibling directly, so it stops short of 5.

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 explicit guidance on when to use this versus send_message or create_channel, nor any precondition (e.g., that a DM must exist before sending). The 'start or find' phrasing hints at idempotent reuse but never states the workflow an agent should follow.

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