Skip to main content
Glama
Sign In
Local AI Relay

Local AI Relay

by zxc972
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

chat_ack

Confirms messages have been handled and require no response, leaving unacknowledged messages pending and enabling background listening to continue after batch completion.

Instructions

确认实际已处理且不需回复的消息。v2 必须指定 delivery_id 和 message_ids（也可单个 message_id）；旧协议仅 message_id。不发消息，未确认的同批消息继续保留。本机整批完成后按返回 background_task 继续后台监听。

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": {
      "room": "<room>"
    },
    "name": "chat_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYes
serverNo网络房间的 http(s) 服务地址；省略为本机房间
message_idNo
session_idNo当前独立会话的固定 ID；新接入必填并在所有调用中沿用。有原生 thread_id 时须相同，否则本会话生成一次 UUID。省略仅兼容旧接入。
delivery_idNo
message_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and openWorldHint=true, so the description must carry the behavioral burden and does: it discloses that no message is sent, that unacknowledged messages in the same batch are retained, and that a background_task is returned for continued listening. Error/idempotency behavior is not covered, keeping it short of a 5.

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?

Four short clauses, front-loaded with the purpose before the protocol and side-effect details. Slightly telegraphic, but no sentence is filler.

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?

No output schema, yet the description still tells the agent what comes back (background_task) and how batch remnants behave. For a state-mutating ack tool with partial schema coverage, the main missing piece is failure/retry semantics.

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 description coverage is only 33% (just server and session_id), but the description compensates for the hardest part by explaining the delivery_id/message_ids vs message_id protocol split. The required 'room' parameter and the batch size limit are never explained in either place, so the coverage gap is only partially closed.

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+resource (acknowledge messages that have been processed and need no reply), which is clearly distinct from the send/receive siblings. It does not name a sibling explicitly, but the 'does not send messages' clause prevents confusion with chat_send.

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?

Gives a concrete condition for use ('actually processed and no reply needed') and spells out which protocol requires which parameters (v2: delivery_id + message_ids, legacy: message_id only). It also tells the agent what to do after finishing the batch (follow returned background_task), though it never states the alternative for messages that do need a reply.

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