AI SENSE Free Public Tools

Read webhook capture

read_webhook_capture

Read-onlyIdempotent

Check whether anything has been sent to a capture URL yet, and read it. The status field is pending or captured. Pending is the ordinary answer before the sender fires and is not a failure. Set wait_seconds from 1 to 25 to wait efficiently for the first request. The call returns early when the capture changes. Zero reads the current state immediately. Unknown and expired IDs fail. No API key, no account and no sign up.

Input Schema

Name	Required	Description	Default
`capture_id`	Yes	The UUID that create_webhook_capture returned.
`wait_seconds`	No	Wait up to this many seconds for a request. Zero returns immediately.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`status`	Yes
`request`	Yes
`capture_id`	Yes
`wait_reason`	Yes
`waited_seconds`	Yes
`expire_datetime`	Yes
`expire_timestamp`	Yes
`created_at_datetime`	Yes
`captured_at_datetime`	Yes
`created_at_timestamp`	Yes
`captured_at_timestamp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 5, 2026

addedInput schema / properties / wait_seconds

Added value: +{
+  "default": 0,
+  "description": "Wait up to this many seconds for a request. Zero returns immediately.",
+  "maximum": 25,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / created_at_datetime
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / created_at_timestamp
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / expire_datetime
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / expire_timestamp
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / ok
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / wait_reason

Added value: +{
+  "enum": [
+    "terminal",
+    "changed",
+    "timeout",
+    "immediate",
+    "unavailable",
+    "stalled"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / waited_seconds

Added value: +{
+  "minimum": 0,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "capture_id",
-  "status",
-  "captured_at_timestamp",
-  "captured_at_datetime",
-  "request"
-]New value: +[
+  "ok",
+  "capture_id",
+  "status",
+  "created_at_timestamp",
+  "created_at_datetime",
+  "captured_at_timestamp",
+  "captured_at_datetime",
+  "expire_timestamp",
+  "expire_datetime",
+  "request",
+  "waited_seconds",
+  "wait_reason"
+]

Changed6 schema fields changedAug 20, 2026

addedInput schema / properties / capture_id / description

Added value: +"The UUID that create_webhook_capture returned."

changedOutput schema / properties / captured_at_datetime / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / captured_at_timestamp / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

changedOutput schema / properties / request / type

Previous value: -"object"New value: +[
+  "object",
+  "null"
+]

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "pending",
+    "captured"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "capture_id",
-  "captured_at_timestamp",
-  "captured_at_datetime",
-  "request"
-]New value: +[
+  "capture_id",
+  "status",
+  "captured_at_timestamp",
+  "captured_at_datetime",
+  "request"
+]

First observedAug 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered; the description still adds real value by explaining that pending is a normal pre-fire state and not a failure, that the call returns early when the capture changes, and that no API key or account is needed. It does not describe what a captured payload contains, though the output schema likely carries that. A solid but not exceptional add-on beyond 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?

Purpose is front-loaded in the first sentence, followed by status semantics, waiting guidance, and error/credential facts. The telegraphic sentence fragments are dense and nearly waste-free, though the style is clipped enough that a slightly more connected phrasing would read better.

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?

With an output schema present, return values need no explanation; the description instead covers the things an agent actually needs to call it correctly: status values, that pending is not an error, wait semantics, and failure modes for unknown/expired IDs. Nothing material is missing for a two-parameter read tool.

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 coverage is 100% and both parameters are documented in the schema, including the 0–25 range and the zero-means-immediate rule, so the baseline is 3. The description restates the range and adds the early-return-on-change behavior, which is marginal value over the schema rather than new semantics.

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?

"Check whether anything has been sent to a capture URL yet, and read it" gives a specific verb (check/read) and resource (capture), and the capture_id schema ties it back to create_webhook_capture. It does not explicitly name the sibling creator/reader pair, but the read-only framing is unmistakable.

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?

It clearly states when to use the wait parameter vs. not ("Set wait_seconds from 1 to 25 to wait efficiently for the first request... Zero reads the current state immediately") and warns that unknown and expired IDs fail. It stops short of naming an alternative tool, but within this tool's scope the when-to-use guidance is explicit.

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

All AI SENSE Free Public Tools tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.