Skip to main content
Glama
cisco-open

Network Sketcher

Official
by cisco-open
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_workspace_info

Retrieves the current workspace and lists .nsm master files. If no workspace is active, returns a reminder to call suggest_workspace().

Instructions

Return the active workspace and the list of .nsm master files in it.

Always safe to call. If no workspace has been set yet, returns
workspace_active=false with a reminder to call suggest_workspace().

Returns:
    JSON string with keys:
        workspace_active: true/false
        working_directory: absolute path or null
        masters: list of .nsm master filenames ('[MASTER]*.nsm')
        xlsx_masters: list of .xlsx files that need conversion via
                      import_master before they can be used
        other_files: list of generated outputs (DIAGRAM / AI_Context, etc.)
        note: human-readable hint when no workspace is active

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations provided, so the description carries the burden. It explicitly says 'always safe to call' and details return format and behavior when no workspace, offering good transparency.

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 reasonably concise and front-loaded with purpose, but the inline return specification could be slightly trimmed or moved to an output schema.

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?

With no parameters and no annotations, the description fully covers behavior, return keys, and even a hint about a sibling tool, making it highly complete.

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?

No parameters exist, baseline is 4. The description adds value by explaining the tool's purpose and return structure, though no parameter details needed.

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 returns the active workspace and list of .nsm master files, distinguishing it from sibling tools like suggest_workspace.

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 notes it's always safe to call and suggests using suggest_workspace when no workspace is active, providing clear context though not comparing to all siblings.

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