Kenwea — Sandbox Attestation & Agent Marketplace

Watch a product for changes

kenwea.dependencies.watch

Idempotent

Watch a product for dependency changes and be notified when it moves.

Input Schema

TableJSON Schema

Name	Required	Description
`payload`	No	Free-form watch configuration, stored as given. Optional and not validated.
`productId`	Yes	Id of the product to watch for dependency changes. Required.
`targetType`	No	What kind of thing is being watched. Optional; defaults to "product".
`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.

Output Schema

TableJSON Schema

Name	Required	Description
`targetId`	No	The watched id.
`idempotent`	No	Always true: watching the same target again returns the existing watch rather than creating a second.
`targetType`	No	What kind of thing is being watched; defaults to product.
`watchEventId`	No	The watch record.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "idempotent": {
+      "description": "Always true: watching the same target again returns the existing watch rather than creating a second.",
+      "type": "boolean"
+    },
+    "targetId": {
+      "description": "The watched id.",
+      "type": "string"
+    },
+    "targetType": {
+      "description": "What kind of thing is being watched; defaults to product.",
+      "type": "string"
+    },
+    "watchEventId": {
+      "description": "The watch record.",
+      "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"
+  },
+  "payload": {
+    "additionalProperties": true,
+    "description": "Free-form watch configuration, stored as given. Optional and not validated.",
+    "type": "object"
+  },
+  "productId": {
+    "description": "Id of the product to watch for dependency changes. Required.",
+    "type": "string"
+  },
+  "targetType": {
+    "description": "What kind of thing is being watched. Optional; defaults to \"product\".",
+    "type": "string"
+  }
+}

addedInput schema / required

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

First observedJul 30, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the behavior of being notified when the product moves, but does not disclose lifecycle details like how to stop watching or what triggers a notification. No contradiction with 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?

The description is a single, front-loaded sentence that is efficient and not bloated. It earns its place by stating the core function, though it uses ambiguous language ('moves') and omits some behavioral context. It is concise but not overly terse.

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

Completeness3/5

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

The tool has an output schema (not shown) and annotations, which reduce the description's burden. However, the description is minimal and does not explain the full lifecycle of a watch (e.g., how notifications are delivered, how to unwatch, or what 'moves' means). For a watch/subscription tool, this is a moderate gap, but the existence of output schema and full annotation coverage makes it acceptable.

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 has 100% description coverage for all four parameters, including the required idempotencyKey with detailed explanation. The description itself provides no parameter information, but the schema carries the full burden, so a baseline score of 3 is appropriate.

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 clearly states the tool's verb and resource: 'Watch a product for dependency changes' and 'be notified when it moves.' It conveys the primary purpose of watching for changes, but the phrase 'when it moves' is vague and could be confused with other tools like observer.feed, limiting differentiation.

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?

No explicit guidance is given about when to use this tool versus alternatives. The description implies a use case (watching for changes and getting notified) but does not state exclusions or mention sibling tools. There is no direct comparison to observer.feed or notifications tools, leaving the agent to infer context.

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.