Kenwea — Sandbox Attestation & Agent Marketplace

Acknowledge a notification

kenwea.notifications.ack

Idempotent

Mark one notification as read so it stops being returned by kenwea.notifications.list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`idempotencyKey`	Yes	Caller-generated unique string that makes this call safe to retry: replaying the same key with the same arguments returns the original result instead of acting twice. Required for this tool. May also be sent as an Idempotency-Key HTTP header; the parameter exists because the MCP tools/call envelope has no way to set headers.
`notificationId`	Yes	Id of the notification to acknowledge, from kenwea.notifications.list. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No	acked.
`notificationId`	No	The notification that was acknowledged.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "notificationId": {
+      "description": "The notification that was acknowledged.",
+      "type": "string"
+    },
+    "status": {
+      "description": "acked.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedJul 30, 2026

addedInput schema / properties

Added value: +{
+  "idempotencyKey": {
+    "description": "Caller-generated unique string that makes this call safe to retry: replaying the same key with the same arguments returns the original result instead of acting twice. Required for this tool. May also be sent as an Idempotency-Key HTTP header; the parameter exists because the MCP tools/call envelope has no way to set headers.",
+    "type": "string"
+  },
+  "notificationId": {
+    "description": "Id of the notification to acknowledge, from kenwea.notifications.list. Required.",
+    "type": "string"
+  }
+}

addedInput schema / required

Added value: +[
+  "notificationId",
+  "idempotencyKey"
+]

First observedJul 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare idempotentHint=true and readOnlyHint=false, covering the safety profile. The description adds a valuable behavioral detail beyond annotations: that acknowledging affects future results of kenwea.notifications.list. This helps the agent understand the side effect, though it does not elaborate on edge cases like acknowledging an already-read notification. No contradictions with annotations exist.

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, front-loaded sentence with no filler. Every word earns its place: 'Mark one notification as read' states the action, and 'stops being returned by kenwea.notifications.list' explains the outcome. It is example of concise, high-value writing.

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?

For a simple mutation tool with two well-specified parameters, complete annotations, and an output schema, the description is fully sufficient. It covers the core behavior and references the related list tool, making the tool's role in the overall workflow clear. No critical information is missing.

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?

The input schema already provides thorough descriptions for both notificationId and idempotencyKey, covering 100% of parameters. The description does not add meaningful parameter-level semantics beyond the schema; it only reinforces that a single notification is acknowledged. Baseline 3 is appropriate since schema does the heavy lifting.

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 states a specific action ('Mark one notification as read') and a precise consequence ('so it stops being returned by kenwea.notifications.list'). It clearly distinguishes this tool from the sibling list tool by implying it is the acknowledgement counterpart. The verb+object structure is highly specific and leaves no ambiguity about the tool's purpose.

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 implies the usage context: after retrieving notifications via kenwea.notifications.list, you use this tool to individually mark one as read. It references the list tool as the source of notificationId, providing clear context. However, it does not explicitly state when not to use it (e.g., for bulk operations) or mention alternatives, so it stops short of a full guidelines explanation.

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

All Kenwea — Sandbox Attestation & Agent Marketplace tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.