Skip to main content
Glama
the-real-talk

the-real-talk

set_layout_positioning

Set a child layer in an auto-layout frame to ABSOLUTE to take it out of flow or AUTO to return it, with optional x, y, and constraints.

Instructions

Set a child of an auto-layout frame to ABSOLUTE (outside the flow) or AUTO, with optional x, y and constraints.

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": {
      "nodeId": "<nodeId>",
      "positioning": "<positioning>"
    },
    "name": "set_layout_positioning"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nodeIdYesID of the child
verticalNo
horizontalNo
positioningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that ABSOLUTE takes the child out of the flow, which is genuinely useful, but it says nothing about the key side effects: whether x/y are ignored or discarded in AUTO mode, whether switching back to AUTO loses the stored offsets, or what the constraints govern relative to the flow.

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?

One front-loaded sentence naming the verb, target, and modes, with no filler. The trailing 'with optional x, y and constraints' is efficient in form but too compressed to be informative, given the low schema coverage.

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?

A six-parameter mutation tool with no annotations and no output schema requires the description to explain mode interactions and constraint semantics, and it does not. An agent would have to guess how x/y, vertical, and horizontal relate to the positioning mode.

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 only 17% (just nodeId), yet the description only repeats 'optional x, y and constraints' without explaining the vertical/horizontal constraint enums (MIN, MAX, CENTER, STRETCH, SCALE) or that x/y likely apply only under ABSOLUTE. It adds essentially no meaning beyond the bare schema for the four undocumented parameters.

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?

States a specific verb (set) and a precise resource: a child of an auto-layout frame, with the two target modes named (ABSOLUTE outside the flow, AUTO). The scope 'a child of an auto-layout frame' is enough to separate it from sibling frame-level tools like set_layout_mode and set_layout_sizing, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The precondition is implied by 'a child of an auto-layout frame', so an agent can infer when the tool is applicable. However, there is no guidance on when to choose ABSOLUTE versus AUTO, whether x/y or constraints should be supplied with a given mode, or which sibling tools to use for the frame itself.

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