Skip to main content
Glama

Tidy Playground nodes or a group

playground_canvas_arrange
Idempotent

Arrange loose nodes as a block, or re-lay out a group’s children, as one revision-checked, idempotent, non-paid revision (the tidy operation of playground_canvas_apply_operations). Give nodeIds or groupId.

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": {
      "projectId": "<projectId>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_canvas_arrange"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdNoExisting canvas group ID to arrange.
nodeIdsNoIDs of the existing canvas nodes to use for this action.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
createdYes
summaryYesHuman-readable summary of the applied canvas operations.
replayedYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Adds real behavioral context beyond the annotations: the change is revision-checked against expectedRevision and consumes no paid credits, and it lands as a single revision. However 'idempotent' merely restates idempotentHint=true, and it does not say whether layout overwrites hand-placed positions or how partial node sets are handled. With annotations already declaring the write/non-destructive profile, this is solid but not rich.

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?

One front-loaded sentence names the action first, then tucks concurrency, cost and idempotency traits into a compact clause, followed by a one-line input rule. No filler and nothing buried.

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?

Adequate for a 5-parameter mutation tool: output schema exists, all parameters are described in the schema, annotations carry the safety profile, and the description covers modes, revision checking and cost. The main missing piece is what happens to existing positions or when both nodeIds and groupId are provided.

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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not encode: nodeIds and groupId are alternatives ('or'), not combinable inputs, and the whole call is a single revision gated on expectedRevision. It does not explain the 60-node cap or behavior when both are supplied.

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?

States a specific verb and resources: arranging loose nodes into a block or re-laying out a group's children. It also positions itself against playground_canvas_apply_operations by naming itself the 'tidy operation' of it, so an agent can distinguish it from the generic operations tool and from per-node layout updates.

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?

Clear usage context is given: use it to block-arrange loose nodes or to re-lay out an existing group's children, and the input selection is stated ('Give nodeIds or groupId'). It does not name exclusions, e.g. that a single node's position should go through playground_canvas_update_node_layout instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.