Skip to main content
Glama

move_element

Moves an element and its children to another location in the same mind map, supporting reordering within a level or promotion and demotion across hierarchy levels.

Instructions

既存マップの要素1件(配下ごと)を、同じマップ内の別の場所へ移動する。階層をまたいだ移動(昇格・降格)も、同じ階層内の並べ替えも、これ1つで行える。

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": {
      "mapId": "<mapId>",
      "elementId": "<elementId>"
    },
    "name": "move_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapIdYeslist_mapsで得たマップのID
elementIdYes移動する要素のID
afterElementIdNo移動先の中で、このIDの要素の直後に置く。先頭に置く場合はnullまたは省略
newParentElementIdNo移動先の親要素のID。マップの最上位へ移動する場合はnullまたは省略

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / properties / afterElementId / description
      Previous value: -"移動先の中で、このIDの要素の直後に置く。先頭に置く場合はnull"New value: +"移動先の中で、このIDの要素の直後に置く。先頭に置く場合はnullまたは省略"
    • changedInput schema / properties / newParentElementId / description
      Previous value: -"移動先の親要素のID。マップの最上位へ移動する場合はnull"New value: +"移動先の親要素のID。マップの最上位へ移動する場合はnullまたは省略"
    • changedInput schema / required
      Previous value: -[
      -  "mapId",
      -  "elementId",
      -  "newParentElementId",
      -  "afterElementId"
      -]New value: +[
      +  "mapId",
      +  "elementId"
      +]
  2. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description bears the full behavioral burden. It usefully discloses that descendants travel with the moved element (配下ごと) and that both promotion/demotion and same-level reordering are supported, but it says nothing about failure behavior, permission or lock requirements, or what the caller gets back when an elementId is invalid.

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, zero filler. The core operation and its scope come first, and the second sentence only adds the capability distinction that actually changes how an agent would call the tool.

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 four-parameter mutation tool with no annotations and no output schema, the description covers the essential semantics: subtree-inclusive move, same-map constraint, and both move modes. The remaining gap is behavioral rather than definitional — no statement of error conditions or side effects — which keeps it short of 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 100%, so mapId, elementId, afterElementId and newParentElementId are already documented, including the null/omitted conventions. The description's two modes map conceptually onto the two optional parameters but add no new syntax or interaction rule (it does not say what happens when both are supplied), so baseline 3 applies.

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 (移動する) and resource (マップの要素1件、配下ごと), and pins the scope to the same map. It also spells out both operating modes (階層をまたいだ昇格・降格 and 同一階層内の並べ替え), so an agent can tell this apart from edit_element or delete_elements without opening any schema.

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?

It makes clear that both reparenting and reordering are handled by this one tool, which implicitly answers 'which tool do I use for a move'. However, it names no alternative and gives no when-not-to-use case (e.g. cross-map moves or content edits, which belong to edit_element), so the routing guidance is implied rather than explicit.

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