Skip to main content
Glama

inspect_clothing_fit

Read-only

Review evaluated garment layers, dependency stacks, seams, attachments, and local edge strain, with an optional motion contact profile to diagnose clothing fit problems.

Instructions

Review evaluated garment layers, dependency stacks, seams, attachments and local edge strain.

Optionally include a motion contact profile. Matched front and side evidence uses the same projection and scale in both panels. The operation restores the original frame.

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

Input Schema

NameRequiredDescriptionDefault
viewsNo
framesNo
profileYes
timeoutNo
blend_fileNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new behavior: the operation 'restores the original frame,' reassuring the agent that scene state is not left mutated, plus the guarantee that matched front and side evidence share projection and scale. It does not cover cost, timeouts, or failure modes, but the added guarantees are substantive.

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

Conciseness3/5

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

Three short sentences with no filler, but the ordering is off: the panel/frame commentary occupies two of three sentences while invocation-critical information is absent. Splitting 'Matched front and side evidence uses the same projection and scale in both panels' across lines hurts scanability.

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 a tool with a required nested profile object and four other undocumented parameters is under-specified for correct invocation. The description covers intent and a state-restoration guarantee but leaves the caller unable to know what to put in profile or how views/frames interact.

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 5 parameters, including a required, free-form nested 'profile' object, so the description must carry the load — and it does not. It never explains views, frames, timeout, blend_file, or the structure of profile, and 'motion contact profile' only loosely gestures at one parameter.

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?

Names a specific verb and resource: reviewing evaluated garment layers, dependency stacks, seams, attachments and local edge strain. That vocabulary distinguishes it from generic siblings like inspect_rig or inspect_spatial_pairs, though it never explicitly says how it differs from them.

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?

The only usage hint is 'Optionally include a motion contact profile,' which signals an optional mode but not when to choose it or when to use this instead of the other inspect_* tools. No prerequisites, preconditions, or exclusions are stated.

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