huly-mcp-selfhost

list_messages

Read-only

Retrieves messages from a Huly channel or direct message by space ID, with an optional limit, so agents can review conversation history and context.

Instructions

List messages in a channel or direct message

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": {
      "spaceId": "<spaceId>"
    },
    "name": "list_messages"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`spaceId`	Yes	Channel or direct-message _id
`workspace`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Nov 12, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description only needs to add context. It adds the scoping fact that results are per-channel/DM, but says nothing about default result size, ordering, or whether results are paginated — meaningful gaps for a list endpoint even with annotations present.

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 front-loaded sentence with zero redundant wording. It is efficient but borders on under-specification rather than demonstrating disciplined conciseness.

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

Completeness2/5

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

For a three-parameter list tool with no output schema and only partial schema coverage, the description should at minimum explain the limit/workspace relationship and expected result shape. As written, an agent cannot tell whether workspace is required for cross-workspace lookups or how many messages come back by default.

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 only 33%: only spaceId is documented ("Channel or direct-message _id"), while limit and workspace have no descriptions in either schema or prose. The description mentions 'channel or direct message' but adds no semantics for limit (default 50, max?) or workspace (does it override or narrow spaceId?), so it fails to compensate for the coverage 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 ("List messages") and scopes it to "a channel or direct message," which is enough to distinguish it from siblings like list_channels or list_thread. It stops short of explicitly contrasting with any named alternative, so it lands at clear-but-undifferentiated.

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 other listing tools, no prerequisites, and no mention of pagination or ordering behavior. The only implied usage is 'you have a channel or DM id,' which the agent must infer from the required spaceId.

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

Deploy Server