Skip to main content
Glama

cancel_style

Stops a running style build or fix job without altering existing styles. Use to halt make_style, fix_style, or continue_style tasks; returns job state or a note if none runs.

Instructions

Stop the style build or fix that's running (make_style, fix_style, continue_style). Nothing is changed: the person's styles stay as they were. Returns the job's state, or a note if nothing runs. To only check progress, use style_status.

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": "cancel_style"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare destructiveHint=false and readOnlyHint=false, and the description adds the key consequence beyond them: 'Nothing is changed: the person's styles stay as they were' — clarifying that only the job halts, not the styles. It also discloses the return value ('the job's state, or a note if nothing runs'), which implicitly covers the idempotentHint=false behavior on repeat calls. Auth/permission requirements are unstated, keeping it short of a 5.

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?

Four short sentences, zero waste: the action and its targets come first, the no-side-effects guarantee second, return behavior third, and the sibling routing last. Every sentence carries distinct information.

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 no-parameter tool with no output schema, the description covers action scope, safety consequences, return shape, and the alternative path. Nothing an agent needs 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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on arguments and instead invests in targeting and side effects.

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 opens with a specific verb ('Stop') applied to a precise resource ('the style build or fix that's running') and enumerates the exact jobs it targets (make_style, fix_style, continue_style). An agent can distinguish this from style_status without consulting either 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?

It states the activation condition (a build or fix is running) and explicitly routes the agent elsewhere when the goal differs: 'To only check progress, use style_status.' That is a named alternative plus the condition that selects it, 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.