Skip to main content
Glama

apply supervisor task

apply_supervisor_task

Activate a candidate only after its preview passes, preserving schedule, mode, and baseline while the next full check verifies recovery.

Instructions

Activate a candidate only after its preview passes. Keeps schedule, mode and baseline. The next full check verifies recovery. 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": "apply_supervisor_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
leaseTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/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 does supply real behavioral context: it preserves schedule, mode and baseline, and states that the next full check verifies recovery, plus a write-scope authorization requirement. It omits whether the activation can be undone, what happens if verification later fails, and what the call returns.

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?

Four short sentences, front-loaded with the prerequisite and the state-preservation guarantee. No filler, though "candidate" and "recovery" are left underspecified for a reader without prior context.

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?

This is an unannotated mutation tool with no output schema and zero parameter descriptions, so the description must do the heavy lifting. It covers preconditions and post-conditions reasonably but leaves the two required parameters and the operation's reversibility/return behavior undocumented.

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 0% for both parameters, so the description is the only source of meaning — but it says nothing about jobId or leaseToken. "Requires a write-scope key" gestures at an authorization credential without mapping it to leaseToken, leaving the 64-character lease-token constraint and the job identifier entirely to the schema.

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?

"Activate a candidate" names a concrete verb and object, and "only after its preview passes" positions it relative to the preview step in the sibling set. It stops short of naming preview_supervisor_task explicitly, so an agent must infer the pairing from the word "preview."

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?

The gating condition ("only after its preview passes") tells the agent when this tool is appropriate and implicitly when it is not — i.e., do not call it before a successful preview. No explicit named alternative or exclusion list is given, and "write-scope key" is the only stated prerequisite.

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