AI SENSE Free Public Tools

Create heartbeat

create_heartbeat

Create a deadline monitor for a job, device or agent that should keep checking in. Call ping_heartbeat before the expected interval plus grace period ends. One missed deadline calls a public HTTP or HTTPS webhook or wakes an active Agent Wake webhook task. The monitor lasts at most 24 hours from creation, and pings cannot extend that limit. The returned heartbeat ID and URLs are bearer secrets. No authentication is required.

Input Schema

Name	Required	Description
`on_miss`	Yes	Exactly one miss target. Use url for a public HTTP or HTTPS webhook with a host name, not an IP address, on port 80 or 443, or wake_task_id for an active Agent Wake webhook task.
`grace_seconds`	Yes	Extra time after the expected check-in before the miss action fires. The expected interval plus grace must not exceed 86400 seconds.
`expect_every_seconds`	Yes	Expected time between check-ins, from 60 seconds to 24 hours.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`late`	Yes
`misses`	Yes
`status`	Yes
`on_miss`	Yes
`delivery`	No
`ping_url`	Yes
`ping_count`	Yes
`status_url`	Yes
`heartbeat_id`	Yes
`grace_seconds`	Yes
`missed_at_datetime`	No
`created_at_datetime`	Yes
`expires_at_datetime`	Yes
`missed_at_timestamp`	No
`created_at_timestamp`	Yes
`expect_every_seconds`	Yes
`expires_at_timestamp`	Yes
`miss_due_at_datetime`	Yes
`terminal_at_datetime`	No
`last_ping_at_datetime`	Yes
`miss_due_at_timestamp`	Yes
`terminal_at_timestamp`	No
`last_ping_at_timestamp`	Yes
`next_expected_at_datetime`	Yes
`next_expected_at_timestamp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / on_miss / description

Previous value: -"Exactly one miss target. Use url for a public HTTP or HTTPS webhook on port 80 or 443, or wake_task_id for an active Agent Wake webhook task."New value: +"Exactly one miss target. Use url for a public HTTP or HTTPS webhook with a host name, not an IP address, on port 80 or 443, or wake_task_id for an active Agent Wake webhook task."

Changed3 schema fields changedSep 9, 2026

changedInput schema / properties / grace_seconds / description

Previous value: -"Extra time after the expected check-in before the miss action fires."New value: +"Extra time after the expected check-in before the miss action fires. The expected interval plus grace must not exceed 86400 seconds."

changedInput schema / properties / on_miss / description

Previous value: -"Exactly one miss target. Use url for a public HTTPS webhook, or wake_task_id for an active Agent Wake webhook task."New value: +"Exactly one miss target. Use url for a public HTTP or HTTPS webhook on port 80 or 443, or wake_task_id for an active Agent Wake webhook task."

changedInput schema / properties / on_miss / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "payload": {},
-      "url": {
-        "format": "uri",
-        "maxLength": 4096,
-        "type": "string"
-      }
-    },
-    "required": [
-      "url"
-    ]
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "wake_task_id": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "required": [
-      "wake_task_id"
-    ]
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "payload": {
+        "description": "Optional JSON body, at most 32768 encoded bytes."
+      },
+      "url": {
+        "format": "uri",
+        "maxLength": 2048,
+        "type": "string"
+      }
+    },
+    "required": [
+      "url"
+    ]
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "wake_task_id": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "required": [
+      "wake_task_id"
+    ]
+  }
+]

AddedSep 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond annotations: the 24-hour maximum lifetime and that pings cannot extend it, that a miss fires a webhook or wakes a task exactly once, that the returned ID/URLs are bearer secrets, and that no authentication is required. These are important operational and safety facts the annotations do not convey.

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?

Front-loads the core purpose in the first sentence and each subsequent sentence carries distinct information (timing, dispatch, lifetime cap, secret handling). It is slightly longer than strictly needed but has no filler.

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 details need not be explained, yet the description still flags the security-sensitive nature of returned values. For a nested-object, three-required-parameter mutation tool, nothing an agent needs before calling 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%, so the baseline is 3. The description echoes the interval-plus-grace timing rule and the on-miss dispatch behavior, but adds little syntax or constraints (port, host, size limits) beyond what the schema already documents in detail.

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?

States a specific verb and resource ('Create a deadline monitor') plus the objects it monitors (job, device, agent). It is clearly distinguishable from siblings ping_heartbeat and read_heartbeat, which are referenced or implied.

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?

Explicitly tells the caller to use ping_heartbeat before the expected interval plus grace period ends, which routes the agent to the correct companion tool. It does not, however, contrast this with alternatives like scheduled webhooks or leases, so it stops short of full when/when-not guidance.

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.