Skip to main content
Glama

scale_object

Adjust an object's dimensions by applying a scale vector to it in Blender, so AI clients can resize models during 3D scene editing.

Instructions

Scale an object.

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": {
      "name": "<name>",
      "scale": "<scale>"
    },
    "name": "scale_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
scaleYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses nothing. It does not say whether existing scale is replaced or multiplied, whether the object must be selected/active, whether child objects are affected, or what the operation returns or how it can be undone.

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

Conciseness2/5

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

Three words is short but this is under-specification, not conciseness. There is no structure to speak of and no information is front-loaded because there is no information.

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

Completeness1/5

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

For a two-parameter mutation tool with zero annotation and zero schema-description coverage, the description is completely inadequate. The presence of an output schema excuses it from explaining return values, but every other thing an agent needs in order to invoke it correctly is missing.

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

Parameters1/5

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

Schema description coverage is 0%: "name" is only typed as a string and "scale" as an array of numbers, with no meaning attached. The description adds nothing — it never clarifies that name is the target object's identifier or that scale is a 3-component XYZ vector (and whether it is a factor or an absolute value).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Scale an object" restates the tool name (scale_object) with no additional specificity: no scope, no units, no indication of what kind of scaling (uniform vs per-axis, local vs world). It is a verb+resource but effectively tautological, and it does nothing to distinguish itself from siblings such as set_object_transform, modify_object, or animate_scale.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from the description why it would call scale_object rather than set_object_transform or modify_object, and there is no statement of when this tool is inappropriate.

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