Skip to main content
Glama

preview supervisor task

preview_supervisor_task

Polls a test, reads visible text and browser targets, and verifies an invariant to validate monitored page behavior; requires a write-scope key.

Instructions

Poll a test, read visible text and browser targets, and verify the invariant. 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": "preview_supervisor_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
leaseTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the write-scope key requirement, which is genuinely useful auth context. However, it doesn't explain whether the call has side effects (polling plus 'verify the invariant' suggests assertions that may fail), what the return looks like, or whether polling blocks or retries.

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?

It is a single tight sentence with the prerequisite stated last, so there is little waste. But the terseness comes at the cost of clarity — 'the invariant' and 'a test' are undefined references that the reader cannot resolve.

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 no annotations, no output schema, and two entirely undocumented parameters, the description is far too thin to let an agent call it confidently. Missing are the meaning of the identifiers, the expected call sequence, and the outcome of a failed verification.

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 description coverage is 0% for both required parameters, so the description must compensate, and it does not. Neither jobId nor leaseToken is mentioned or explained; 'write-scope key' only loosely gestures at a credential, leaving the 64-character lease token semantics undocumented.

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

Purpose3/5

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

The description names a sequence of actions (poll a test, read visible text and browser targets, verify the invariant), which hints at a preview/verification step for a supervisor task, but it never says 'supervisor task' or what is being tested. 'Poll a test' is ambiguous and doesn't clearly separate this from siblings like get_supervisor_task or device_screenshot_supervisor_task.

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?

The only conditional information is the prerequisite 'Requires a write-scope key'. There is no statement of when to use this versus apply_supervisor_task, get_supervisor_task, or the device_* variants, and no mention of what state is expected beforehand.

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