Skip to main content
Glama

Heartbeat foreground control

foreground_control_heartbeat
Destructive

Renew the current foreground-control lease to keep an active task authorized, and optionally update the overlay task text.

Instructions

Renew the current foreground-control lease and optionally update the task shown in the overlay.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "leaseId": "<leaseId>"
    },
    "name": "foreground_control_heartbeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNo
leaseIdYes
deviceIdNo
deviceNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds useful context that the task update is optional (overlay content changes only when 'task' is supplied), but it never explains why the operation is flagged destructive or what state is lost on expiry.

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?

A single front-loaded sentence with the primary action first and the optional side effect clearly marked. No waste, though it is arguably too terse for a mutation tool.

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?

For a mutating lease tool with four undocumented parameters, no output schema, and a surprising destructiveHint=true, the description omits lease lifetime/failure semantics, device parameter meaning, and any indication of required permissions.

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

Parameters2/5

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

Schema coverage is 0%, so the description carries the burden and only partially compensates: it implies the 'leaseId' renewal and the 'task' overlay text, but says nothing about 'deviceId' or 'deviceName', leaving two of four parameters undocumented anywhere.

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?

States a specific verb ('Renew') and resource ('foreground-control lease'), plus the optional secondary effect on the overlay task. This clearly separates it from foreground_control_acquire/release/pause, though it does not name those siblings explicitly.

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 when-to-use guidance, no mention of the sibling tools, and nothing about the heartbeat cadence, lease expiry window, or what happens if the lease has already lapsed. The agent is left to infer that this is a periodic keep-alive call.

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

Deploy Server

Other Tools