Skip to main content
Glama

export_device_table_html

Export an interactive HTML device table preview with four tabs from a .nsm master file, generating a self-contained file for offline sharing.

Instructions

Export an interactive HTML Device Table preview from a .nsm master.

Generates a single self-contained HTML file with four tabs (L1 Table /
L2 Table / L3 Table / Attribute) whose layout, styling, and behaviour
match the Online edition's Device Preview screen (sticky-header table,
per-tab CSV / HTML download buttons, URL-hash initial tab selection).

The output file is written next to the master as
``[DEVICE_TABLE]{basename}.html`` and contains no external CDN /
script references, so it can be opened directly from disk or shared
as a single artifact.

PREREQUISITE: call get_ai_context(master) (or at least
get_network_state(master)) once per session for this master so you
understand the data being exported.

Args:
    master: Master filename inside the working directory
            (e.g. '[MASTER]office.nsm') or an absolute path inside
            the active workspace.

Returns:
    A summary describing the generated file and its size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
masterYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It details output characteristics (single self-contained HTML, four tabs, no external references, specific file naming) and the prerequisite. It does not mention if the tool overwrites existing files or handle errors, but it sufficiently discloses the main behavior.

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 well-structured and front-loaded: purpose, output details, prerequisite, parameter. Every sentence adds value without redundancy. It is concise yet comprehensive, fitting the tool's complexity.

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 single parameter, clear prerequisite, and output summary mention, the description is largely complete. It lacks potential error scenarios or size/boundary notes, but overall it provides sufficient context for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains the 'master' parameter (filename inside working directory or absolute path, .nsm master). This adds meaning beyond the schema, though it could specify the expected file extension more explicitly.

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 starts with a clear action verb and resource: 'Export an interactive HTML Device Table preview from a .nsm master.' It specifies the output format and distinct tabs, distinguishing it from sibling tools like export_diagram and export_master_xlsx.

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 description explicitly states a prerequisite: 'call get_ai_context(master) (or at least get_network_state(master)) once per session.' This provides clear when-to-use context. However, it does not mention scenarios where the tool should not be used or suggest alternatives beyond the prerequisite.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cisco-open/network-sketcher'

If you have feedback or need assistance with the MCP directory API, please join our Discord server