Skip to main content
Glama
Sign In
NetMap — Network Diagram MCP

NetMap — Network Diagram MCP

by den-indance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

map_set_zoom

Adjust the network diagram canvas zoom level (0.1–3.0) to focus on specific nodes or view the entire topology.

Instructions

Set canvas zoom level (0.1–3.0).

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": {
      "zoom": "<zoom>"
    },
    "name": "map_set_zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoomYesZoom level, e.g. 1.0 = 100%, 0.5 = 50%

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds the valid range (0.1–3.0), which is useful, but does not disclose what happens with out-of-range values, whether the operation is absolute or incremental, or whether it affects the current view only.

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 containing exactly the necessary information: the action (set), the target (canvas zoom level), and the valid range (0.1–3.0). There is no unnecessary repetition or filler.

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 setter with one parameter, the description plus schema is largely complete. It clearly communicates the action and the constrained range, and no output schema is expected. It could mention clamping or validation behavior, but the core functionality is adequately covered.

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 schema already fully describes the 'zoom' parameter with an example (1.0 = 100%, 0.5 = 50%), so the description adds minimal semantic value beyond the range. The description's range complements the schema but does not significantly enhance understanding.

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 'Set canvas zoom level' with a specific verb and resource, and it is distinguished from siblings like map_set_canvas_offset and map_zoom_to_fit by explicitly targeting zoom level. The inclusion of the range (0.1–3.0) further specifies the scope of the operation.

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 the tool is for setting the canvas zoom level but does not explicitly state when to use it versus alternatives such as map_zoom_to_fit or map_get_view. It provides no exclusions, prerequisites, or guidance on choosing between related tools.

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

Deploy Server

Other Tools