Skip to main content
Glama
cisco-open

Network Sketcher

Official
by cisco-open
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

build_default_outputs

Generate a complete set of deliverables for a network diagram master: combined multi-layer HTML viewer, device table, and AI context file in a single call.

Instructions

Generate the default deliverable bundle for a .nsm master.

Runs the following three steps in a single call:
  1. export combined_diagram --type all_areas
     Produces FOUR artifacts in one shot:
       - [L1_DIAGRAM]AllAreasTag_<base>.svg  (per-layer side effect)
       - [L2_DIAGRAM]AllAreas_<base>.svg     (per-layer side effect)
       - [L3_DIAGRAM]AllAreas_<base>.svg     (per-layer side effect)
       - [L1L2L3_DIAGRAM]AllAreas_<base>.html (combined tabbed HTML
         viewer; primary deliverable)
     The combined HTML embeds all three layer SVGs in a self-contained
     page with three switchable tabs (L1 / L2 / L3) styled to match
     the Device Table viewer. Per-layer SVGs are reused if already
     present in the workspace; missing ones are generated as needed.
  2. export_device_table_html
     (file: [DEVICE_TABLE]<base>.html)
  3. (re-)generate AI Context file
     (file: [AI_Context]<base>.txt)

Each step is judged independently; if one step fails the remaining
steps still execute and the per-step status is reflected in the
returned summary. The summary lists six rows -- one per individual
artifact -- so callers can see which layers (if any) failed even when
the combined HTML succeeded.

Per-area combined HTMLs (e.g. ``[L1L2L3_DIAGRAM]<area>_<base>.html``)
are NOT generated by default. If you need one, request it explicitly
via ``run_commands(["export combined_diagram --type per_area --area
<name>"])`` after this tool returns.

Call this ONCE as the final step after constructing or substantially
updating a network so that diagrams, the Device Table preview, and the
AI Context bundle are all refreshed in lock-step. Prefer this tool
over individually calling export_diagram / export_device_table_html /
get_ai_context for routine finalization.

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

Returns:
    A multi-line summary listing each artifact's status, the generated
    file path, and a trailing 'Summary: N/6 succeeded.' line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
masterYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses independent step execution, artifact generation, reuse of per-layer SVGs, and that failure in one step doesn't halt others. Describes return format as a multi-line summary with per-artifact status. Fully transparent with no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively long but well-structured with numbered steps, bullet points, and clear separation of concerns. Each sentence serves a purpose, though some minor redundancy could be trimmed. Front-loaded with main purpose.

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

Completeness5/5

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

Given the tool's complexity (multi-step, multiple artifacts, error handling), the description is complete: covers all steps, artifacts, error behavior, output format, and links to alternatives. Output schema exists (though not detailed) but description adequately describes return summary. No gaps.

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?

Only one parameter, master, with 0% schema description coverage. The description adds meaning by specifying accepted formats: 'Master filename inside the working directory (e.g. [MASTER]office.nsm) or an absolute path inside the active workspace.' This clarifies type and constraints beyond the schema.

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 generates a default deliverable bundle for a .nsm master, listing three specific steps with artifact types. It distinguishes from sibling tools like export_diagram, export_device_table_html, and get_ai_context by recommending this tool for routine finalization rather than individual calls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Call this ONCE as the final step after constructing or substantially updating a network.' Also specifies when not to use (per-area combined HTMLs) and directs to use run_commands for that case. Provides clear guidance on preference over individual export calls.

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