NetMap — Network Diagram MCP

Overview Schema Source Related Servers Discussions Admin

map_move_node

Reposition any node on your network diagram canvas to new coordinates while preserving all its other properties, enabling precise layout adjustments.

Instructions

Move a node to new canvas coordinates without changing any other fields.

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>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "map_move_node"
  }
}

Input Schema

Name	Required	Description
`x`	Yes	New canvas X position
`y`	Yes	New canvas Y position
`id`	Yes	Node id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description must disclose behavior itself. It clearly states the tool only changes coordinates and preserves other fields, which is valuable. It doesn't mention return values, error conditions, or whether the node must exist, leaving some ambiguity.

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?

The description is a single sentence, immediate and memorable, with no wasted words. Every element contributes to understanding.

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?

Given the tool's simplicity and full schema coverage, the description covers the essential behavior. It could be enhanced with a note about return values or error handling, but the core use case is clear.

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 100% with descriptions for all three parameters. The description adds no extra parameter-level detail beyond the schema, 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 uses the specific verb 'Move' with the resource 'node' and clarifies the scope ('to new canvas coordinates without changing any other fields'). This clearly distinguishes it from sibling tools like map_update_node and map_move_sticky.

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 phrase 'without changing any other fields' strongly implies this tool is for position-only updates, contrasting with update_node. However, it doesn't explicitly name alternatives or state when not to use it.

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