agentwebmap

Test notification

test_notification

Owner only. Send a test event to the configured webhook and/or email to confirm the wiring (once per 10 minutes).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	A domain name such as example.com (no scheme, no path).
`api_key`	Yes	The owner API key issued by verify_domain (awm_key_...).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 19, 2026

addedInput schema / properties / api_key / maxLength
```
Added value: +200
```
addedInput schema / properties / api_key / minLength
```
Added value: +1
```
addedInput schema / properties / domain / maxLength
```
Added value: +253
```
addedInput schema / properties / domain / minLength
```
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"
+}

First observedOct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: the owner-only authorization requirement and the once-per-10-minutes rate limit, both of which an agent needs before calling.

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 the authorization constraint first, followed by the action and the rate limit. Zero wasted words.

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

Completeness4/5

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

For a two-parameter test tool with an output schema covering return values, the description supplies the key operational facts: auth requirement, side effect, and rate limit. It leaves minor edges (e.g., behavior when no webhook/email is configured) unspecified, but nothing essential 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?

Schema description coverage is 100% and both parameters (domain, api_key) are fully documented in the schema. The description adds no syntax or format detail beyond the schema, so the baseline 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?

States a specific verb and resource: sending a test event to the configured webhook and/or email to confirm wiring. An agent can distinguish it from most siblings, but it never names or contrasts the closest sibling test_watch, so the differentiation is only implicit.

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?

Gives clear context for when to use it (to confirm the notification wiring) and states the 'Owner only' precondition plus a rate limit. It does not name an alternative or exclusion, which keeps it short of a 5.

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.