Skip to main content
Glama

ack

Marks addressed messages as read in your mailbox so agents can track handled messages and coordinate their work.

Instructions

Mark addressed messages as read in your mailbox.

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": {
      "ids": "<ids>"
    },
    "name": "ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and openWorldHint=false, so the mutation and closed-world profile is known without the description. The description adds almost nothing beyond that: it does not state idempotency, what happens with unknown/already-read IDs, partial-failure behavior, or the effect of the 100-item cap on batching.

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 short sentence with no filler, and the core action is front-loaded. It is efficient but so terse that the brevity borders on under-specification for a mutating tool.

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 state-changing tool with an undocumented required array parameter, batching limits, and no output schema to explain results, the description leaves out too much. It does not say what a successful or failed ack returns, nor how to recover the IDs it needs.

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 0% and the single required parameter 'ids' is never mentioned in the description, so the agent gets no explanation of what the integers identify or where to obtain them. Only a loose inference (message IDs of addressed messages) is available.

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 pairs a specific verb with a specific resource and outcome: mark addressed messages as read in the user's mailbox. This disambiguates the terse name 'ack' well enough to act on, though it does not name or contrast any sibling (inbox, post, lock).

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 when-to-use guidance at all: nothing says when a message becomes 'addressed', whether acking is required or optional, or which sibling to call first to discover message IDs. Only the barest context is implied by the phrase 'addressed messages'.

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