Skip to main content
Glama

Turn Quick on or off

set_quick_autowork
Idempotent

Turn Quick working on its own on (enabled=true) or off (enabled=false). On: at once, and again on each new save, Quick analyses the user's saved jobs and strong radar matches, prepares resume suggestions, tailors a resume copy when the job is worth it and writes a cover letter, spending the plan's own limits and keeping part of them for the user; it never applies. Off: it stops taking new jobs; ready work stays, and the weekly find Quick prepares at no cost comes back. Sprint and Career only: on the free plan turning on answers payment_required. Same switch as the Quick page in settings. Args: {enabled}.

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": {
      "input": "<input>"
    },
    "name": "set_quick_autowork"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
enabledYes
includedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare mutation/idempotency/safety flags, while the description adds the behaviour that matters: what Quick does on enable, that it spends plan limits while reserving part for the user, that it never applies on the user's behalf, that disabling preserves existing ready work, and the plan-gated error. That is substantial context beyond the annotations and consistent with destructiveHint=false.

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 core action and the true/false mapping are front-loaded, and each clause carries distinct information (effects, limits, never-applies, off-behaviour, plan gate, settings-page equivalence). The semicolon-chained phrasing is dense and takes effort to parse, but nothing is redundant.

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

Completeness5/5

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

For a one-parameter toggle with annotations and an output schema, the description covers everything an agent needs: state semantics, side effects, billing/limit implications, plan gating and the resulting error path. No relevant decision input is missing.

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

Parameters4/5

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

There is a single boolean, and the description repeatedly anchors its meaning (enabled=true = on with the full described effects, enabled=false = paused), reinforcing the schema's short property description. With one parameter and modest schema coverage there is little more semantic depth to add.

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

Purpose5/5

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

The description uses a specific verb+resource ('Turn Quick working on its own on/off') and immediately defines what the on and off states mean, which separates it from nearby toggles like set_radar_auto_search or set_search_pause.

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?

It clearly states the conditions for each state (on: analyses saved jobs and radar matches; off: stops new jobs, keeps ready work, restores the free weekly find) plus a plan prerequisite (Sprint and Career only, payment_required on free). It does not explicitly route to a sibling such as get_quick_work for inspecting current state, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.