NetMap — Network Diagram MCP

by den-indance

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

map_switch_sheet

Switch to another network diagram sheet, saving the current sheet state first to prevent data loss.

Instructions

Switch the active sheet. Saves current sheet state first.

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": "map_switch_sheet"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Sheet id to switch to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses an important behavior — that current sheet state is saved before switching — which adds value beyond the basic action. This helps agents understand side effects, though more details (e.g., error handling) could be included.

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 two short sentences, each earning its place. No filler, redundant phrasing, or unnecessary detail.

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 low complexity (one parameter, fully documented schema, no output schema), the description is sufficiently complete: it states the action, the target (active sheet), and a key behavioral guarantee (saving state). No obvious gaps that would cause misuse for a simple switch operation.

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%, with the 'id' parameter fully documented as 'Sheet id to switch to'. The description adds no extra meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 clearly states the tool's function: 'Switch the active sheet.' This is a specific verb+resource combination that distinguishes it from sibling tools like list, create, rename, or delete sheet operations.

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?

The description implies usage (switching sheets) but provides no explicit when-to-use guidance, exclusions, or alternatives. The 'saves current sheet state first' is a behavioral note, not usage direction. General context is clear, but no explicit guidance is given.

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