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

NetMap — Network Diagram MCP

by den-indance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

map_export_sheet

Export network diagram sheet data as JSON, including auto-connections. Defaults to active sheet, or specify a sheet ID.

Instructions

Export sheet data as JSON including auto-connections. Defaults to active sheet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "map_export_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSheet id (omit for active sheet)

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?

No annotations are provided, so the description carries the full burden. It discloses that the output is JSON, includes auto-connections, and targets the active sheet by default. However, it does not state whether the operation is read-only, what the response structure looks like, or any potential side effects, leaving some transparency gaps.

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, tightly-worded sentence. It front-loads the core action and format, then adds the default behavior without any redundancy. Every word contributes value.

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 tool with one optional parameter and no output schema, the description covers the essential context: what is exported, in what format, the inclusion of auto-connections, and the default sheet. It lacks some behavioral details but is sufficiently complete for a simple export 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?

The input schema already has 100% coverage for the 'id' parameter with the description 'Sheet id (omit for active sheet)'. The tool description essentially restates this by saying 'Defaults to active sheet', adding no new parameter semantics. 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 verb 'Export', the resource 'sheet data', and the format 'JSON', along with a distinguishing feature 'including auto-connections'. It also clarifies the default behavior, which helps differentiate it from sibling tools like map_get_sheet_data or map_export.

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 provides a usage hint by noting the default to the active sheet, but it does not explicitly state when to use this tool over alternatives like map_export or map_get_sheet_data. The intended usage is implied rather than clearly laid out.

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