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

TableJSON Schema

Name	Required	Description
`on_miss`	Yes	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.
`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

TableJSON 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.

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.7/5.0

Behavior4/5

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

Annotations already indicate this is a write operation (readOnlyHint=false, destructiveHint=false). The description adds valuable behavioral context: the monitor lasts at most 24 hours, pings cannot extend that limit, and the returned heartbeat ID and URLs are bearer secrets. It also explains the miss action (webhook or wake task). This goes beyond the annotations and helps the agent understand side effects and security implications.

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?

The description is concise and front-loaded with the core purpose. It covers the key behavioral constraints (24-hour limit, bearer secrets, no auth required) in a compact, well-structured paragraph. Every sentence adds value, and the structure flows logically from purpose to usage to constraints.

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 tool's complexity (nested on_miss object, two mutually exclusive target types, time constraints) and the presence of an output schema, the description is complete. It explains the miss action, the time limits, the security model, and the relationship between parameters. An agent has enough information to call this tool correctly without additional context.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds context by explaining the relationship between expect_every_seconds and grace_seconds ('The expected interval plus grace must not exceed 86400 seconds') and by clarifying the on_miss target options ('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'). This adds meaning beyond the raw schema.

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 clearly states the tool's purpose: 'Create a deadline monitor for a job, device or agent that should keep checking in.' It uses a specific verb ('create') and resource ('deadline monitor'), and distinguishes it from siblings like ping_heartbeat and read_heartbeat by explaining the creation role and the monitoring behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent when to use this tool: 'Call ping_heartbeat before the expected interval plus grace period ends.' It also explains the miss behavior and the 24-hour limit, which clarifies when this monitor is appropriate. It doesn't explicitly name alternatives, but the context of creating a monitor versus pinging it is clear.

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

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.