Skip to main content
Glama

Keep how layers were arranged

save_layer_arrangement

Saves moved and hidden layer positions for image cards, keeping arrangements intact after reload and on the dashboard.

Instructions

Used by the image card to keep what the user moved and hid in a layer set, so it is there after a reload (and on the dashboard). Not useful to call directly.

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": {
      "id": "<id>"
    },
    "name": "save_layer_arrangement"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the set's base.
movesNo
hiddenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the key traits: the caller is the image card, and the effect is durable across reloads and visible on the dashboard. It does not say whether 'moves' replaces or merges with existing arrangement, nor what happens on failure or missing set id, leaving a mutation-semantics gap.

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 tight sentences with the persistence rationale front-loaded and the internal-use caveat handled in a short trailing clause. No filler, though the parenthetical '(and on the dashboard)' is minor decoration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with a nested object parameter, no annotations and no output schema, the description covers the 'why' and 'who calls it' well but not the write semantics or return behaviour. Acceptable given the tool is explicitly not for direct invocation, but not fully self-contained.

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 coverage is low (33%) — only 'id' is documented — so the description must compensate. It does partially: 'what the user moved and hid' maps onto the 'moves' and 'hidden' parameters, giving an agent a usable mental model, but the nested 'moves' object shape and whether 'id' is the layer set id or a base-image id remain unspecified.

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?

Names a specific effect: persisting what the user moved and hid in a layer set so it survives a reload and appears on the dashboard. The resource (layer set arrangement) and verb (keep/save) are clear, though it doesn't explicitly differentiate itself from save_mask or save_selection beyond the 'layer set' framing.

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?

"Used by the image card... Not useful to call directly" is an unusually explicit when-NOT-to-use signal, telling an agent to skip this tool in favour of UI-driven flows. It stops short of naming an alternative to call instead, so it falls short of the top mark.

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