lnkz-mcp

Append messages to a conversation

append_messages

Add new turns to an existing conversation, keeping a thread continuous when continuing in another client.

Instructions

Adds new turns to an existing conversation, which is how a thread continued in a second client stays one thread.

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": {
      "conversationId": "<conversationId>",
      "messages": "<messages>"
    },
    "name": "append_messages"
  }
}

Input Schema

Name	Required	Description	Default
`messages`	Yes
`conversationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotations already indicate a non-read-only, non-idempotent mutation. The description adds the context of thread continuation but does not elaborate on side effects, failure modes, or rate limits. Since annotations cover the core behavioral cues, the description provides marginal extra transparency.

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?

The description is a single, focused sentence with no redundancy. It packs the core action and a motivating use case efficiently.

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

Completeness4/5

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

It provides enough context for an agent to understand the typical use case (appending messages from a second client). It does not cover edge cases like missing conversation or message validation, but those are partially addressed by the schema. Overall, it is suitably complete for the tool's simplicity.

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?

The description never names or explains the parameters. It refers to 'new turns' and 'existing conversation' but does not clarify that conversationId is the target identifier or that messages is an array of objects with role/content fields. The schema is left to carry all parameter meaning, but schema coverage is 0%, so the description fails to compensate.

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

Purpose5/5

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

The description clearly states the action (adds new turns), the target resource (existing conversation), and the purpose (keeping a thread unified across clients). This distinguishes it from siblings like save_conversation or import_conversation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete usage scenario ('how a thread continued in a second client stays one thread') that implies when to use this tool. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a perfect score.

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