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

NetMap — Network Diagram MCP

by den-indance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

map_get_sheet_data

Retrieve all nodes, connections, stickies, and notes from a specific sheet in a network diagram, defaulting to the active sheet when no ID is provided.

Instructions

Return nodes/connections/stickies/notes for a specific sheet (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_get_sheet_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSheet id (omit for active sheet)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/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 the default active sheet behavior and the types of data returned. However, it doesn't describe the return format, potential empty results, or any read-only guarantees, leaving some behavioral aspects unaddressed.

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 that clearly states the action and resource without any redundant words. It is highly concise and structured effectively.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with one optional parameter and no output schema, the description covers what data is returned and the default behavior. However, it omits details about the structure of the returned data and any edge cases, which is notable given the absence of an output schema.

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 documents the single parameter 'id' with a description that matches the tool description's defaulting behavior. With 100% schema coverage, the description adds no additional parameter meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns nodes, connections, stickies, and notes for a specific sheet, providing a specific verb and resource. It distinguishes itself from sibling getters like map_get_notes and map_get_all_connections by covering multiple entity types, though it doesn't explicitly name alternatives.

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 'for a specific sheet (defaults to active sheet)' provides clear context on when to use this tool. It implies use for retrieving sheet content, and the optional id parameter covers the default behavior. However, it doesn't explicitly state when not to use it or mention alternative 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