Skip to main content
Glama

preview_cloth_corrective

Read-only

Stage a pose-dependent cloth corrective locally to check clearance, trim, and deformation before committing. Review live candidates or file-only assessments without saving changes.

Instructions

Stage a local, pose-dependent displacement and check clearance, trim and deformation.

Requires an authored mask and protected vertex groups. A feasible live preview returns a one-use candidate ID. A file preview returns assessment only. Neither saves the file.

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": {
      "profile": "<profile>"
    },
    "name": "preview_cloth_corrective"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewsNo
profileYes
timeoutNo
blend_fileNo
expected_sessionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false; the description adds real behavioral context beyond that: the operation requires an authored mask and protected vertex groups, does not save the file in either mode, and returns a one-use candidate ID that is consumed once. The apparently mutating verb "stage" is reconciled by the explicit "Neither saves the file", so there is no contradiction with the read-only hint.

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?

Front-loaded with the action and the checks performed, then the prerequisites, then the two outcome modes. Every sentence carries information; only the slight terseness of the final line ("Neither saves the file") costs it a point of clarity.

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

Completeness3/5

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

An output schema exists, and the description still helpfully summarizes return semantics (candidate ID vs assessment-only). But for a tool with a required nested profile object and two undocumented optional parameters, the definition stops short of what an agent needs to construct a valid call.

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%, so the description must carry parameter meaning and largely does not. The required nested "profile" object (with additionalProperties) is never explained, and timeout and expected_session are untouched; only the file-versus-live distinction hints at blend_file's role.

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?

"Stage a local, pose-dependent displacement and check clearance, trim and deformation" gives a specific verb (stage) and a concrete resource plus the three things being validated. It is clearly a preview/non-committing operation, which distinguishes it in spirit from the apply_* siblings, though no sibling is named explicitly.

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?

Prerequisites are stated (authored mask and protected vertex groups), and the description distinguishes two modes: a live preview that yields a one-use candidate ID versus a file preview that returns assessment only. However, it never says when to prefer this over apply_cloth_corrective or how the candidate ID feeds the apply step, so the routing guidance is implied rather than explicit.

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