Skip to main content
Glama

Scale Shape

scale_shape

Scale a shape uniformly or per axis to bake a standalone solid, optionally around a pivot center; the source geometry is consumed into the scaled copy.

Instructions

Scale a shape uniformly or per-axis, baking a fresh static solid.

Scaling breaks parametric history, so this produces a standalone Part::Feature (not a linked/parametric feature); the source object is hidden since its geometry is consumed into the scaled copy.

handle: source shape handle. factor: scalar for uniform scale, or [sx, sy, sz] for per-axis scale. All factors must be > 0. center: optional [x, y, z] mm pivot to scale about; when omitted the scale is about the world origin (so the shape also moves away from/toward origin). name: object label (default 'Scaled').

Lengths in mm. Returns {handle, name, volume, factor} where factor is the normalized [sx, sy, sz] applied and volume (mm^3) equals the source volume times sxsysz.

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": {
      "handle": "<handle>",
      "factor": "<factor>"
    },
    "name": "scale_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoScaled
centerNo
factorYes
handleYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important non-obvious effects: parametric history is broken, the source object is hidden, and the operation returns a standalone Part::Feature. It also describes the return payload and how volume relates to the applied factors, which is valuable behavioral context.

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?

The definition is front-loaded with the core purpose, then organized into a compact parameter list and return-value note. Every section is useful and there is no redundant restatement of schema or annotations.

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?

The tool has no output schema, but the description supplies the return shape: {handle, name, volume, factor}. Combined with annotations covering safety and a complete explanation of the mutation, parameters, and return values, an agent has enough information to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is only 20%, the description compensates by explaining every core parameter: handle is the source shape handle, factor accepts a scalar or [sx, sy, sz] and must be > 0, center is an optional mm pivot defaulting to world origin, and name defaults to 'Scaled'. It even clarifies the origin behavior and returned normalized factor.

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 first sentence gives a specific verb and resource: scaling a shape uniformly or per-axis and producing a fresh static solid. It also distinguishes the result from parametric/linked geometry by naming Part::Feature and explaining that the source is hidden, which helps separate it from transform or copy-style siblings.

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

Usage Guidelines4/5

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

The description gives clear usage context by warning that scaling breaks parametric history and therefore produces a standalone solid. It does not explicitly name alternatives such as transform or copy_shape or state when not to use this tool, so it falls short of full alternative-routing guidance.

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

Deploy Server

Other Tools