Skip to main content
Glama
dha-aa

AE Motion MCP

by dha-aa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Link Layers

link_layers
Destructive

Parent layer_ids to parent_id (null unlinks), or to a new_null created at their average position (3D if any of them is), stacked above them. jump true keeps each child's own transform values (it can visibly move).

Instructions

Parent layer_ids to parent_id (null unlinks), or to a new_null created at their average position (3D if any of them is), stacked above them. jump true keeps each child's own transform values (it can visibly move). Self-links, cycles, locked layers or mixed comps are refused before anything changes.

Input Schema

NameRequiredDescriptionDefault
jumpNo
new_nullNo
layer_idsYesSame comp
parent_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.23.0
    • removedInput schema / properties / parent_id / anyOf
      Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / parent_id / type
      Added value: +[
+  "integer",
+  "null"
+]
  2. First observedv2.22.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (destructive=true, idempotent=false), it discloses atomic refusal conditions (self-links, cycles, locked layers, mixed comps rejected before any change) and the subtle side effect that jump=true can visibly move children. These are exactly the mutation risks an agent needs.

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?

Two dense sentences that front-load the primary operation and pack real information into every clause. The opening 'Parent layer_ids to parent_id' is slightly telegraphic, requiring the reader to parse the grammar, but no sentence is wasted.

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 destructive, nested-object, no-output-schema tool, it covers mode selection, side effects, and failure guarantees. It does not describe what is returned or whether the operation is confirmed/reversible, which is a modest remaining gap.

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

Parameters4/5

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

With only 25% schema coverage, the description compensates well: parent_id's null-unlink behavior, new_null's average-position and 3D derivation, and jump's transform-preserving semantics are all explained. It leaves new_null.name and new_null.position unexplained, so not a full 5.

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 description states a specific verb (parent/link) and resource (layer_ids) plus the two target modes (an existing parent_id or a newly created null). No sibling among the listed tools performs parenting, so the operation is unmistakable without opening the schema.

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 explicitly distinguishes the three modes: passing a parent_id, passing null to unlink, and supplying new_null to create a parent at the children's average position. It does not name an alternative tool or state prereqs for choosing one mode over another, which caps it below 5.

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