Wever Labs Agent Products

Callback Health Monitor

wever_callback-health-monitor

Destructive

Paid URL: 0.10 USDC per call on Base; 10 signed-wallet free calls shared over rolling 30 days. Read the backend 402 body for x402 terms. Send a bounded HTTPS callback probe and persist the actual response, timing and exact acknowledgment check. Retrieve prior observations without resending. Operating boundary: Supply one public HTTPS callback URL and the acknowledgment you expect. The service makes one request, saves its timing and response, and lets you retrieve that observation later. Each new probe is an explicit call. POST /api/callback-health-monitor. Existing product credentials, signed mandates, and single-use action grants remain required where applicable. This adapter grants no authority and never supplies server credentials. Wallet-authenticated bounded operations service with durable records. See /api/operations-contract for exact schemas, verified scope and unavailable capabilities.

Input Schema

Name	Required	Description	Default
`mode`	Yes
`usage`	No
`probe_id`	No
`callback_url`	No
`idempotency_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 3, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

removedInput schema / description

Removed value: -"The existing product POST body. Supply its documented mode, arguments, and required signed authority or grant. The product validates its full contract."

removedInput schema / maxProperties
```
Removed value: -64
```
removedInput schema / minProperties
```
Removed value: -1
```

addedInput schema / oneOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "callback_url": {
+        "maxLength": 2048,
+        "minLength": 1,
+        "type": "string"
+      },
+      "idempotency_key": {
+        "pattern": "^[a-zA-Z0-9_-]{1,96}(?![\\s\\S])",
+        "type": "string"
+      },
+      "mode": {
+        "const": "probe"
+      },
+      "usage": {
+        "enum": [
+          "synthetic",
+          "operational"
+        ]
+      }
+    },
+    "required": [
+      "mode",
+      "idempotency_key",
+      "callback_url",
+      "usage"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "mode": {
+        "const": "retrieve"
+      },
+      "probe_id": {
+        "pattern": "^[a-f0-9]{64}(?![\\s\\S])",
+        "type": "string"
+      }
+    },
+    "required": [
+      "mode",
+      "probe_id"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / callback_url

Added value: +{
+  "maxLength": 2048,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / idempotency_key

Added value: +{
+  "pattern": "^[a-zA-Z0-9_-]{1,96}(?![\\s\\S])",
+  "type": "string"
+}

addedInput schema / properties / mode / enum

Added value: +[
+  "probe",
+  "retrieve"
+]

removedInput schema / properties / mode / maxLength
```
Removed value: -128
```
removedInput schema / properties / mode / minLength
```
Removed value: -1
```
removedInput schema / properties / mode / type
```
Removed value: -"string"
```

addedInput schema / properties / probe_id

Added value: +{
+  "pattern": "^[a-f0-9]{64}(?![\\s\\S])",
+  "type": "string"
+}

addedInput schema / properties / usage

Added value: +{
+  "enum": [
+    "synthetic",
+    "operational"
+  ]
+}

addedInput schema / required
```
Added value: +[
+  "mode"
+]
```

First observedSep 29, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The description adds substantial context beyond annotations: exact pricing (0.10 USDC per call on Base, 10 free signed-wallet calls per rolling 30 days), durable record persistence, credential requirements, and the assurance that the adapter grants no authority and never supplies server credentials. That said, some of this is boilerplate ('signed mandates, single-use action grants... where applicable') that is vague about the actual auth requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is stated early, and the 'Operating boundary' framing is useful. But pricing and contract boilerplate ('See /api/operations-contract for exact schemas, verified scope and unavailable capabilities') consume space without helping selection or invocation, and the capability is restated multiple times.

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?

With a destructive annotation, no output schema, and 5 parameters at 0% schema coverage, the description should do more. It covers when the probe runs and that records are retrievable, but leaves the usage enum, idempotency semantics, and probe_id format unexplained, and references a nonexistent acknowledgment parameter.

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%, so the description must carry the parameter burden, and it largely doesn't. It never explains the 'usage' enum (synthetic vs operational), the 'idempotency_key' pattern or purpose, or the 64-hex-char 'probe_id'. Worse, it instructs the caller to 'supply ... the acknowledgment you expect', yet no acknowledgment parameter exists in the schema, which will mislead an agent constructing the call.

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 uses specific verbs and resources: 'Send a bounded HTTPS callback probe', 'persist the actual response, timing and exact acknowledgment check', and 'Retrieve prior observations without resending'. This distinguishes the probe and retrieve behaviors clearly. It doesn't explicitly contrast with siblings, but the resource (HTTP callback health) is distinct enough from the payment/workorder tools.

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?

The 'Operating boundary' paragraph implies when to use each mode: supply a URL for a new probe, or retrieve a prior observation without resending. However, it never names an alternative tool or states when not to use this one, and the guidance is framed as capability description rather than selection criteria.

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

All Wever Labs Agent Products 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.

Callback Health Monitor

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources