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

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

pin_message

Pin a message or comment to its channel to keep it visible, or set pinned=false to unpin it.

Instructions

Pin a message or comment in its channel; pinned=false unpins

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

Input Schema

NameRequiredDescriptionDefault
pinnedNo
messageIdYesMessage id (list_messages, list_comments, list_thread)
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the toggle semantics and the 'in its channel' scoping, but it omits what happens when the target is already pinned, whether pinning a comment differs from a message, and any permission or rate-limit considerations.

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 compact sentence with the core action front-loaded and the toggle modifier second. No filler, no repetition of the title.

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 three-parameter mutation tool with no output schema, the description covers the main action and toggle but leaves the required workspace parameter unexplained and says nothing about the result of the operation or idempotency. Adequate but with visible gaps.

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 only 33%, so the description must carry weight; it does explain the 'pinned' boolean behavior (false unpins), which the schema leaves as an undocumented default. The required 'workspace' parameter is undocumented in both schema and description, and the messageId description is the only schema-side help, leaving a real gap.

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 description gives a specific verb and resource ('Pin a message or comment in its channel') plus the inverse operation ('pinned=false unpins'), which is enough to distinguish it from siblings like delete_message or update_message. It stops short of naming an alternative tool or stating the scope boundary explicitly, so it is clear but not maximally differentiated.

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?

The 'pinned=false unpins' clause implicitly tells an agent how to toggle the state, which is useful implied guidance. However, there is no explicit statement of when to use this versus delete_message or update_message, and no prerequisites such as required permissions or whether the caller must be the author.

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