Skip to main content
Glama

monitor_heartbeat_sync

Sync periodic system metrics (errors, latency, CPU, memory, queue depth) into your session for proactive drift and burnout detection.

Instructions

Sync periodic heartbeat metrics into the current session for proactive drift and burnout detection. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional: extra context
statusNoOptional: short status label (stable / degraded / critical / burnout)
session_idYesYour active session ID
queue_depthNoOptional: queue depth/backlog
risk_signalNoOptional: what feels risky right now? (1 sentence)
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
cpu_usage_pctNoOptional: CPU usage in percent (0-100)
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
latency_ms_p95NoOptional: p95 latency in ms
errors_last_hourNoOptional: error count in the last hour
interval_secondsNoOptional: heartbeat interval in seconds
memory_usage_pctNoOptional: memory usage in percent (0-100)
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
cron_runs_last_hourNoOptional: cron/job scheduler runs in the last hour
jobs_failed_last_hourNoOptional: failed jobs/tasks in the last hour
cron_failure_last_hourNoOptional: failed cron/job runs in the last hour (alias for jobs_failed_last_hour)
cron_success_last_hourNoOptional: successful cron/job runs in the last hour (alias for jobs_success_last_hour)
jobs_success_last_hourNoOptional: successful jobs/tasks in the last hour
cron_failures_last_hourNoOptional: failed cron/job scheduler runs in the last hour
Behavior2/5

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

Annotations show readOnlyHint=false, implying mutation, but the description simply says 'sync... into the current session' without elaborating on side effects, permissions, or rate limits. It adds minimal behavioral context 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?

The description is very short and front-loaded with the core purpose. The extra 'Free.' is unnecessary but does not harm. Could benefit from more structure, but it is concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (19 parameters, no output schema, minimal annotations), the description omits crucial information such as return values, behavior with omitted parameters, and impact on session state. It is not complete enough for reliable agent invocation.

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 parameter descriptions are detailed in the schema. The tool description does not add new meaning; it only states 'Free.' which is irrelevant to parameters. Baseline of 3 is appropriate.

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?

The description clearly states the tool syncs periodic heartbeat metrics into the current session for drift and burnout detection. The verb 'sync' and resource 'heartbeat metrics into the current session' are specific. However, it does not differentiate from similar siblings like 'attune_heartbeat', leaving some ambiguity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No mention of prerequisites, context, or when not to use. The description is purely functional without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/delx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server