Skip to main content
Glama

agent_ack_message_ids

[STATE] Mark 1..50 received IDs handled or dismissed, even unopened IDs. Skipped messages stay pending. Idempotent and independent of bulk acknowledgment. Returns acknowledged/unavailable/error per ID; retry errors. Shared 5000/day budget. Sent copies cannot be acknowledged.

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": {
      "message_ids": "<message_ids>"
    },
    "name": "agent_ack_message_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idsYes1..50 received IDs to mark handled or dismissed, including unopened IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior1/5

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

Annotation contradiction: the description states 'Idempotent' while the annotations declare idempotentHint=false, so an agent cannot trust whether repeated calls are safe. The description otherwise discloses side effects, per-ID statuses, retry semantics, a shared rate budget, and sent-copy restrictions, which would be strong behavioral transparency, but the direct contradiction forces score 1.

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?

Every clause carries distinct operational meaning: scope, skip behavior, idempotency, per-ID returns, retry guidance, rate budget, and the sent-copy exclusion. The main action is front-loaded in the first clause. The description is dense but not padded.

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

Completeness5/5

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

With no output schema, the description still provides the high-level per-ID statuses ('acknowledged/unavailable/error') and instructs the agent to retry errors. It covers limits (1..50, shared 5000/day budget), idempotency, and an important precondition (sent copies cannot be acknowledged). For a single-parameter state-changing tool, this is complete.

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 100%, and the schema already documents message_ids as '1..50 received IDs to mark handled or dismissed, including unopened IDs,' so the baseline applies. The description repeats this scope and adds behavior-level context such as retry errors, the shared budget, and sent-copy restrictions, but it adds no additional parameter-specific meaning. It neither harms nor significantly improves on the schema.

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 opens with a specific state-changing verb ('Mark') and a precise resource ('1..50 received IDs') with clear acceptance criteria ('handled or dismissed, even unopened IDs'). It also distinguishes itself from the bulk-acknowledgment sibling by noting it is independent of bulk acknowledgment, so an agent can tell this tool's scope apart from agent_ack_messages.

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?

The description gives clear situational context: specific received IDs can be acknowledged or dismissed, skipped messages remain pending, and sent copies cannot be acknowledged, which tells the agent when the tool is inapplicable. It mentions independence from bulk acknowledgment, implying a related alternative, but it does not explicitly name the sibling or say 'use X instead'. This is clear context with a minor omission of explicit alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources