Skip to main content
Glama

arrange_items

Arrange selected Miro items or a frame's items into a tidy grid, row, or column with uniform cells and gaps, preserving order and skipping connectors.

Instructions

Auto-layout items into a tidy grid/row/column (uniform cells = largest item, gap between). Give ids (kept in that order) or parentId (all items in that frame, current reading order). Connectors are skipped; they follow their items. Starts at the current top-left of the items. Returns {moved, columns}.

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": "arrange_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapNo
idsNo
layoutNogrid
columnsNo
parentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, so the agent already knows this is a non-destructive mutation; the description adds real value on top by explaining that positions are rewritten starting at the current top-left, that connectors are skipped and follow their items, and by naming the return shape {moved, columns}. It stops short of saying whether the operation is undoable or what happens on overlapping/colliding items, which is the remaining behavioral gap.

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?

Four short sentences, each front-loaded with its subject (layout model, targeting mode, connector exception, starting point, return value). No filler and no restatement of the tool name.

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 five-parameter mutation tool with no output schema, the description supplies the geometry rules, the two targeting modes, the connector exception, and the return shape — enough to call it correctly. It could still say more about how columns interacts with layout and whether the move is reversible, but nothing essential is missing.

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?

Schema description coverage is 0%, so the description carries the burden, and it covers most of it: ids (order preserved), parentId (whole frame, reading order), layout (grid/row/column implied by the opening), and gap ("gap between"). The columns parameter is only hinted at via the return value and its interaction with layout is never explained, which keeps this below a 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 opens with a specific verb and resource — auto-layout items into a grid/row/column — and immediately qualifies the layout model (uniform cells sized to the largest item, gap between). This clearly distinguishes it from the CRUD siblings like create_items or update_items, which do not reposition items.

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 gives explicit selection rules for the two targeting modes: pass ids to keep a specific order, or pass parentId to lay out every item in a frame in current reading order. That resolves the main ambiguity an agent would face. It does not state when to prefer this over other tools or what happens if both ids and parentId are supplied, but no sibling performs layout, so the gap is minor.

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