NetMap — Network Diagram MCP

Overview Schema Source Related Servers Discussions Admin

map_set_canvas_offset

Pan the network diagram canvas to an absolute pixel offset to instantly jump to any exact location for detailed inspection.

Instructions

Pan canvas to an absolute pixel offset.

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

Input Schema

Name	Required	Description	Default
`x`	Yes	Horizontal offset in pixels
`y`	Yes	Vertical offset in pixels

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 2, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing side effects, reversibility, or view-related consequences. The term 'absolute' adds some context but no deeper behavioral transparency.

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 front-loaded sentence with no filler. It conveys the essential action and target resource efficiently.

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 simple two-parameter setter, the description covers the core behavior adequately. It lacks notes about view-only effects or prerequisites, but given the tool's simplicity and sibling context, it is reasonably complete.

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?

The input schema already describes both parameters clearly (horizontal/vertical offset in pixels). The description adds the 'absolute' qualifier, which helps interpret x/y as absolute coordinates, but otherwise relies on the schema's 100% coverage.

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 a specific verb ('pan') and resource ('canvas'), and clarifies the coordinate system with 'absolute pixel offset'. This clearly distinguishes it from sibling tools like map_set_zoom or map_move_node.

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: call this when you need to set the canvas to an absolute pixel position. However, there is no explicit comparison with alternatives or any when-not-to-use guidance, so it's only at the implied level.

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