Skip to main content
Glama

Rename or reposition a Playground node

playground_canvas_update_node_layout
Idempotent

Update only the common title and/or canvas position of any user-facing Playground node. This is non-paid, revision-checked, idempotent, and returns the previous values for a follow-up undo command. Node-specific content is not changed.

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>",
      "nodeId": "<nodeId>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_canvas_update_node_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoHuman-readable label to display for this item in Playground.
nodeIdYesExisting canvas node ID returned by canvas_read, node search or creation.
positionNo
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
nodeIdYes
previousYes
replayedYes
revisionYes
updatedFieldsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real, non-redundant behavior: the operation is non-paid, it is revision-checked (conflict handling), and it returns previous values enabling an undo command. It omits permission/auth requirements, which keeps it at 4.

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?

Two sentences, both front-loaded: the first states exactly what is mutated and the behavioral contract, the second closes the one loophole (node-specific content). Every clause carries information; nothing is padding.

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?

With an output schema present, return-value explanation is not required, and annotations carry the safety profile. The description still covers scope, revision-conflict handling, idempotency, cost, and undo support for a 6-parameter nested-schema mutation. Missing only auth/permission preconditions for a full 5.

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 83%, so the schema already documents projectId, nodeId, expectedRevision, idempotencyKey and the nested position x/y. The description only gestures at title and position in prose without adding format or constraint detail beyond the schema. Baseline 3 is appropriate.

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 names a specific verb pair (rename/reposition) and a precise resource scope ('only the common title and/or canvas position of any user-facing Playground node'). The closing clause 'Node-specific content is not changed' implicitly separates it from the sibling playground_canvas_update_text, so the agent can route without opening either 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?

The word 'only' plus the exclusion of node-specific content makes the boundary clear: use this for title/position, use a text-specific tool for content. It also flags the revision-checked workflow (read revision, expect revision_conflict). It stops short of explicitly naming the alternative tool or stating when not to use this at all, so it lands at 4 rather than 5.

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.