Skip to main content
Glama

AI SENSE Free Public Tools

by com.aisenseapi

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: call it directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capture_idYesThe UUID that create_webhook_capture returned.
wait_secondsNoWait up to this many seconds for a request. Zero returns immediately.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
statusYes
requestYes
capture_idYes
wait_reasonYes
waited_secondsYes
expire_datetimeYes
expire_timestampYes
created_at_datetimeYes
captured_at_datetimeYes
created_at_timestampYes
captured_at_timestampYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changed
    • 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"
+]
  2. Changed6 schema fields changed
    • 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"
+]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds significant behavioral detail beyond that: status semantics, pending not being a failure, early return when capture changes, zero meaning immediate read, unknown/expired IDs failing, and no-auth direct invocation. There is no contradiction with the annotations.

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?

Four compact, front-loaded sentences cover purpose, status semantics, waiting behavior, edge cases, and authentication. Every sentence earns its place; there is no filler or redundancy.

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?

Given the output schema, full parameter documentation, and read-only/idempotent annotations, the description covers all necessary operational details: status interpretation, waiting strategy, early return, failure cases, and invocation prerequisites. Nothing essential for correct use is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the description adds further meaning: it explains the effective use of wait_seconds (1-25 for efficient waiting), the early-return behavior, and that zero reads the current state immediately. This goes beyond the schema's basic parameter constraints and enriches agent understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Check whether anything has been sent to a capture URL yet, and read it.' It clearly distinguishes the tool as a read/status operation and defines the status values (pending/captured), preventing confusion with capture creation or other sibling tools.

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?

The description gives practical usage guidance: pending is a normal state, wait_seconds can be used to wait efficiently with early return on change, and zero returns immediately. It also explains that no API key, account, or signup is needed. It stops short of explicitly naming create_webhook_capture as the complementary tool, but the create/read relationship is clear from the sibling context.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool belongs to a clearly separated resource family: leases, heartbeats, human approvals, webhook captures, temporary data, and small utilities. Even similar-sounding tools like create_agent_wake and create_heartbeat are differentiated by their descriptions: durable task completion versus deadline monitoring.

Naming Consistency5/5

Tool names consistently use a snake_case verb_noun pattern, such as acquire_lease, create_heartbeat, read_webhook_capture, and store_temporary_data. Paired operations read naturally, with only a minor and acceptable variation between get_current_time and the read_* tools.

Tool Count4/5

At 18 tools, this is slightly above the ideal 3-15 range, but the server intentionally bundles several independent public utilities rather than one narrow domain. Each tool has a distinct purpose, so the count feels full but not bloated.

Completeness4/5

Core workflows are well covered: leases support acquire, renew, release, and complete; heartbeats support create, ping, and read; captures, approvals, and temporary data have create/read or store/read pairs. There are no explicit delete, cancel, or update tools, but the 24-hour expiration design makes those gaps manageable.

Resources