Skip to main content
Glama

events_ack

Destructive

Marks displayed events as read for a specific consumer session up to a given event ID, helping agents track processed notifications during simulation workflows.

Instructions

Mark displayed events as read for one platform/session.

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": {
      "consumer": "<consumer>",
      "through": "<through>"
    },
    "name": "events_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
throughYes
consumerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds nothing about that: it does not say whether acknowledgement is irreversible, whether the underlying events are consumed or merely flagged, or what a repeated call does. Framing a destructive, non-idempotent operation as merely 'mark as read' arguably understates the effect, though it does not directly contradict the annotations.

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 the action front-loaded and no filler. It is efficiently written, though its brevity reflects under-specification rather than disciplined editing.

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?

An output schema exists so return values need not be described, but for a destructive, non-idempotent mutation with two entirely undocumented required parameters the definition is too thin. It should at minimum explain the 'through' boundary and what acknowledgement does to the events.

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% for two required parameters, so the description must carry the burden and does not. 'One platform/session' loosely gestures at 'consumer', but 'through' is never explained (presumably a sequence/offset boundary), leaving an agent guessing at the correct value for a required argument.

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 ('Mark ... events as read') plus a scope qualifier ('displayed ... for one platform/session'), so an agent can tell this is an acknowledgement/write tool rather than a query. It does not name or differentiate against the sibling 'events' tool, and 'displayed' is left undefined, but the core action is identifiable.

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, no statement of prerequisites (e.g. having listed events first), and no mention of when not to call it or what to use instead. The only contextual hint is the phrase 'displayed events', which implies a prior listing step but does not state it.

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