moddl

Scale elements

scale_elements

Scales bodies (guid, guids or set) by a factor, uniform or per element axis (local, not world), in place about the body center by default; about placement_origin holds the placement point. An element with body_gap has no reliable center and is refused there (a body swept along a directrix: the exact centre): name about. New revision, effect report (n_changed, rejected, cloned, carried). A call that succeeds is not a job that's done. Target: guid, guids or a set from find_elements/get_selection, never a filter. Beyond the named: PLAN_REQUIRED, run its plan_id with expect_beyond.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scale_elements"
  }
}

Input Schema

Name	Required	Description
`set`	No	A set id from find_elements or get_selection: writes exactly the elements seen there, nothing that matches later. An element changed since reading is rejected alone; the others are written
`guid`	No	One element (GlobalId)
`note`	No	Your note, stored with the new revision
`about`	No	Fixed point: center (default, hull centre: in place) or placement_origin
`guids`	No	These elements (GlobalIds)
`factor`	No	Uniform, or [fx,fy,fz] along each element's own axes (its local placement), not world axes
`dry_run`	No	Preview: the planned effect and a plan_id, nothing written
`plan_id`	No	Execute exactly the plan a dry_run returned, all or nothing; the plan holds target and fields. Plans that clone the same shared object (type, material) run one after the other: plan the second after the first ran, else PLAN_CHANGED
`request_id`	No	Your id for this call: a repeat answers the first result and writes nothing
`expect_count`	No	With set: how many elements the set holds - guards against a mixed-up set id
`expect_beyond`	No	With plan_id: how many elements the plan reaches beyond those named (n_beyond of PLAN_REQUIRED or the dry_run)
`expect_contacts`	No	Intended contacts: checks.contacts splits into as_expected, missing, surprises; an omitted kind is not judged

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false) the description discloses that a new revision is created, the effect report fields (n_changed, rejected, cloned, carried), that elements with body_gap are refused, that stale elements are rejected individually while others are still written, that plan_id execution is all-or-nothing, and that request_id makes repeats no-ops. This is substantive behavioral context that the structured fields do not carry.

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?

Purpose is front-loaded, but the prose degrades into fragments ("New revision, effect report (n_changed, rejected, cloned, carried). A call that succeeds is not a job that's done.") and the closing "Beyond the named: PLAN_REQUIRED..." line is cryptic. Sentences mostly carry information, but the compression makes the definition harder to parse than a slightly longer, structured version would be.

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

Completeness4/5

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

For a 12-parameter mutation tool with no output schema, the description covers the important ground: what changes, what gets written into history, how refusal works, and how to preview/commit via plans. It stops short of naming the verification siblings (check_contacts/accept_contacts) that "a call that succeeds is not a job that's done" implies, leaving that next step implicit.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents factor, about, set, plan_id, expect_count and the rest. The description adds only modest interpretation ("in place about the body center by default", "local, not world") and the PLAN_REQUIRED/expect_beyond coupling, which is close to a restatement of the schema text.

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 first clause gives a specific verb and resource ("Scales bodies ... by a factor") plus the two scoping modes (uniform vs per-axis local), which separates it from move_elements/rotate_elements/mirror_elements without naming them. The parenthetical enumeration of target forms (guid, guids or set) is precise, but the dense telegraphic phrasing slightly muddies an otherwise clear statement of purpose.

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?

It states where targets may come from ("a set from find_elements/get_selection, never a filter") and outlines the dry_run -> PLAN_REQUIRED -> plan_id workflow including expect_beyond. What it does not do is explicitly contrast itself with the sibling transforms (move_elements, rotate_elements, mirror_elements), so an agent must infer when scaling is the right operation rather than moving/rotating.

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

All moddl tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?