Skip to main content
Glama

cancel_cloth_corrective

Discard a live cloth corrective preview using its candidate ID and expected session to cancel an in-progress simulation preview.

Instructions

Discard a live cloth corrective preview.

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": {
      "candidate_id": "<candidate_id>",
      "expected_session": "<expected_session>"
    },
    "name": "cancel_cloth_corrective"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidate_idYes
expected_sessionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the mutation profile is covered. The description adds only the 'live' qualifier and says nothing about the non-idempotent behavior, whether the operation errors on a stale or missing preview, or what state is left behind after discarding.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification given the two undocumented required parameters.

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?

An output schema exists, so return values need not be explained, but the input side is bare: two required parameters with no semantics and no guidance on failure modes for a state-mutating cancel operation. For a tool that must be invoked with a session token, this leaves meaningful gaps.

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% and both parameters are required, so the description carries the full burden for candidate_id and expected_session — yet it mentions neither. The meaning of expected_session (apparently a staleness/concurrency guard) is completely undocumented anywhere the agent can see.

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?

The description states a specific verb and resource ('Discard a live cloth corrective preview'), which clearly separates it from apply_cloth_corrective and preview_cloth_corrective in the sibling list. It stops short of naming those siblings explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: the word 'live' suggests this applies to a preview that is currently active, and the 'discard' framing implies it is the inverse of applying. There is no explicit statement of when to prefer this over apply_cloth_corrective, nor what happens if no live preview exists.

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