Skip to main content
Glama

device_status supervisor task

device_status_supervisor_task

Reads recovery browser screenshot, status, and pending command; test a repair with the returned deviceId before applying after Save and Close. Requires a write-scope key.

Instructions

Read the recovery browser screenshot, status and pending command. After Save and Close, test a repair with the returned deviceId before applying. Requires a write-scope key.

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": {
      "jobId": "<jobId>",
      "leaseToken": "<leaseToken>"
    },
    "name": "device_status_supervisor_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
leaseTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions a write-scope key and a post-save repair test sequence, but it does not disclose read-only versus mutating behavior, side effects, failure handling, or what the returned status and pending command imply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the three sentences are disjointed and shift from reading a screenshot to testing a repair. The core purpose is not front-loaded clearly, and some wording reads more like workflow narration than tool definition.

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 tool with two required parameters, no annotations, no output schema, and no parameter descriptions, the definition is too thin. It gives a partial workflow hint but leaves an agent without enough information to invoke it confidently.

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

Parameters1/5

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

The schema has 0% description coverage for two required parameters, jobId and leaseToken. The description does not explain either parameter and only mentions a returned deviceId, which is not an input parameter, so it fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it reads a recovery browser screenshot, status, and pending command, but it does not state a single clear verb-and-resource purpose. It is also hard to distinguish from sibling tools such as device_screenshot_supervisor_task or device_command_supervisor_task because no explicit differentiation is provided.

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

Usage Guidelines3/5

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

The description provides some context: it says to use this after Save and Close and that a write-scope key is required. However, it does not explain when to choose this tool over related supervisor or test tools, so the guidance remains implicit.

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