Skip to main content
Glama

reorder_items

Move selected board items to the front or back to fix z-order layering, such as revealing text hidden behind a shape.

Instructions

Bring items to the front or send them to the back (z-order), e.g. text hidden behind a shape.

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": {
      "ids": "<ids>",
      "to": "<to>"
    },
    "name": "reorder_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds that the change is purely a stacking-order change rather than a content change, which is useful. It does not disclose what happens to the relative order of the remaining items, whether the change is undoable, or whether items must share a parent/group — meaningful gaps for a mutating tool.

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?

A single sentence with the operation front-loaded and the clarifying example trailing it. No filler, no redundant restatement of the tool name.

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 two-parameter, non-destructive tool with no output schema, the annotations plus this sentence cover the essentials. However, the multi-id case (the most likely source of incorrect invocation) is left entirely unaddressed, so an agent could call it correctly-shaped but with wrong semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 full burden of explaining the two parameters, and it adds essentially nothing. It never says whether the order of the ids array determines the resulting stacking order among multiple items, nor whether ids must belong to the same parent. Only the front/back enum is indirectly echoed by the prose.

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 concrete verb pair ("Bring items to the front or send them to the back") plus the resource (items) and names the underlying concept (z-order), which is more than a restatement of the name. The parenthetical example ("text hidden behind a shape") pins down what z-order means in this domain. It does not explicitly contrast with the sibling arrange_items, so it stops short of a 5.

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?

Usage is implied rather than stated: the layered-object example tells the agent this is for fixing stacking/occlusion problems. There is no explicit when-not guidance and no named alternative (e.g. arrange_items for positional layout), so the agent must infer which sibling to pick from the names alone.

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