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 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 HTTPS webhook, 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.
`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. Dates show when Glama detected each change.

AddedSep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=false, etc.), it discloses the 24-hour lifetime cap, that pings cannot extend it, that returned IDs/URLs are bearer secrets, and that no auth is required. These are operationally important behaviors not visible in schema.

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?

Five concise sentences, each adding material information: purpose, usage, miss action, lifetime limit, and security posture. No filler or repetition of schema details.

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?

For a creation tool with output schema, annotations, and a rich parameter schema, the description covers lifecycle, failure behavior, secrets handling, and authentication requirements. Nothing essential is missing for an agent to invoke it correctly.

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 covers 100% of parameters with clear descriptions, so baseline is 3. The description adds useful cross-parameter context by explaining the expected interval plus grace period relationship and the on_miss firing behavior, nudging it above baseline.

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: 'Create a deadline monitor' for a job, device or agent. It differentiates itself from siblings by naming ping_heartbeat as the companion check-in tool and describing the miss behavior.

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 create the monitor ('for a job, device or agent that should keep checking in') and instructs to call ping_heartbeat before the deadline. It lacks explicit exclusions or alternative tool routing, but the intended workflow is unambiguous.

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

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.

Create heartbeat

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources