Skip to main content
Glama

continue_style

Resume a stopped style build or fix in the same Claude session from where it stopped. Requires confirmation before using more Claude usage; fails if nothing can be continued.

Instructions

Resume a style build or fix that stopped part way (style_status says canContinue: true), in the same Claude session, from where it stopped. Uses more of the person's Claude usage, so the first call only says what will happen; call again with confirm: true after they agree. Fails if nothing can be continued. To start a new style use make_style; to repair a finished one use fix_style.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "continue_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNotrue only after the person agreed to use more Claude usage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / confirm / description
      Added value: +"true only after the person agreed to use more Claude usage."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the cost model (consumes more of the person's Claude usage), the unusual two-phase call pattern where the first call is a dry-run notice, and the error condition. The annotations only say it is a non-read-only, non-destructive, non-idempotent, closed-world call; the description adds the operational behavior an agent must know.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the resume action and its precondition, followed by cost/confirmation behavior and then disambiguation. No sentence is redundant or restates the title.

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 resume tool with no output schema, the description covers the trigger condition, cost implications, consent protocol, failure mode, and sibling routing. Nothing an agent needs in order to invoke it correctly 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?

Schema coverage is 100% and the single parameter is already documented, so the baseline is 3. The description nevertheless adds meaning by explaining the ordering: call once without confirm, then call again with confirm: true after the person agrees, which clarifies the parameter's gating role rather than just its type.

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?

Names a specific verb and resource ('Resume a style build or fix that stopped part way') and explicitly separates itself from the two nearest siblings, make_style and fix_style. An agent can pick this tool without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition (style_status says canContinue: true), an explicit failure case (fails if nothing can be continued), and routes to alternatives for new builds and repairs. It also spells out the two-step confirmation flow, leaving nothing to inference.

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