agentwebmap

Test watch

test_watch

Send a test event to a watch's webhook (once per 10 minutes).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`secret`	Yes
`watch_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 19, 2026

addedInput schema / properties / secret / maxLength
```
Added value: +200
```
addedInput schema / properties / secret / minLength
```
Added value: +1
```
addedInput schema / properties / watch_id / minimum
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "attempts": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "channel": {
+                "type": "string"
+              },
+              "detail": {
+                "type": "string"
+              },
+              "event": {
+                "type": "string"
+              },
+              "ok": {
+                "type": "boolean"
+              },
+              "watch_id": {
+                "type": "integer"
+              }
+            },
+            "required": [
+              "event",
+              "ok",
+              "detail"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "domain": {
+          "type": "string"
+        },
+        "watch_id": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "domain",
+        "attempts"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": true,
+      "properties": {
+        "detail": {
+          "type": "string"
+        },
+        "domain": {
+          "type": "string"
+        },
+        "error": {
+          "type": "string"
+        },
+        "hint": {
+          "type": "string"
+        },
+        "retry_after_seconds": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

AddedOct 19, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds a genuine behavioral trait beyond them: the rate limit of one test per 10 minutes. It still doesn't say what happens on failure or whether the webhook delivery is retried, keeping it short of a 5.

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?

A single front-loaded sentence with no filler. The parenthetical constraint is compactly attached rather than given its own sentence.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a two-parameter tool with 0% schema coverage, the definition leaves the meaning of both required inputs and the failure behavior of the test delivery unspecified.

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 neither parameter is described in the schema, so the description carries the full burden. It mentions 'watch's webhook' and 'a test event' but never explains that watch_id identifies the watch or what secret is for (auth token, webhook signing secret). Two required parameters remain semantically opaque.

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 states a specific verb+resource: send a test event to a watch's webhook. An agent can immediately tell what the call does. It does not differentiate itself from the sibling test_notification, which is a plausible source of confusion, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is for validating a watch's webhook configuration. The parenthetical rate limit gives a useful operating constraint, but there is no explicit when-to-use, when-not-to-use, or naming of the alternative test_notification tool.

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

All agentwebmap tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.