Skip to main content
Glama

apply_cloth_corrective

Recheck and apply a still-current live cloth corrective in Blender by validating the candidate and expected session before applying it with native Undo support.

Instructions

Recheck and apply a still-current live corrective with native Blender Undo.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNo
candidate_idYes
expected_sessionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.1/5.0
Behavior4/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 safety profile is partly covered. The description still adds genuine context beyond them: it performs a freshness recheck before mutating, and the change lands on Blender's native undo stack, meaning the apply is reversible via Ctrl+Z. It omits what happens on a stale candidate and whether the corrective is consumed afterward.

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, and the two key behaviors (recheck, native undo) appear immediately. It is efficient but borders on under-specified rather than wasteful; nothing needs trimming, something needs adding.

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 described, but this is a non-idempotent mutation with two required parameters at zero schema coverage and no failure-mode guidance. For a commit-style operation, an agent needs to know what happens if the candidate is stale, whether the corrective is consumed, and what expected_session guards against; none of that is present.

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% across three parameters, so the description carries the full explanatory burden and mostly does not. It never mentions candidate_id, expected_session, or timeout; expected_session in particular is an opaque token whose concurrency/versioning role an agent cannot infer. Only "still-current" loosely gestures at why a session expectation is required.

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 pairs specific verbs ("recheck and apply") with a specific resource (a live cloth corrective), so an agent knows this commits a pending corrective rather than previewing or cancelling one. It stops short of explicitly naming the sibling alternatives (preview_cloth_corrective, cancel_cloth_corrective), so differentiation is inferred from the verb 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 Guidelines2/5

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

There is no explicit statement of when to use this versus preview_cloth_corrective or cancel_cloth_corrective. The word "still-current" hints at a precondition (the candidate must not be stale) but the description never says what to do when that precondition fails or which tool to call first.

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