Skip to main content
Glama

drawing

Create, list, update, delete, or batch create shapes and text labels for network topology diagrams in GNS3 projects.

Instructions

Manage drawings (CRUD operations)

v0.47.0: CRUD-style consolidation of create_drawing, update_drawing, delete_drawing, and create_drawings_batch.

Actions: - list: List all drawings in a project - create: Create new drawing (rectangle, ellipse, line, text) - update: Update existing drawing properties - delete: Delete drawing (WARNING: destructive, cannot be undone) - batch: Create multiple drawings with two-phase validation

Returns: JSON with drawing info or batch operation results

Examples: # List drawings >>> drawing(action="list", project_id="abc-123") >>> drawing(action="list", project_id="abc-123", format="json")

# Create rectangle
>>> drawing(action="create", drawing_type="rectangle", x=100, y=100, width=200, height=100)

# Create text label
>>> drawing(action="create", drawing_type="text", x=175, y=140, text="Router1", z=1)

# Update drawing position
>>> drawing(action="update", drawing_id="abc123", x=200, y=200)

# Delete drawing
>>> drawing(action="delete", drawing_id="abc123")

# Create multiple drawings
>>> drawing(action="batch", drawings=[
...     {"drawing_type": "rectangle", "x": 100, "y": 100, "width": 200, "height": 100},
...     {"drawing_type": "text", "x": 175, "y": 140, "text": "Router1", "z": 1}
... ])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX coordinate (start point for line, top-left for others)
yNoY coordinate (start point for line, top-left for others)
zNoZ-order/layer (default: 0 for shapes, 1 for text)
rxNoHorizontal corner radius (rectangle only)
ryNoVertical corner radius (rectangle only)
x2NoEnd X coordinate (line only)
y2NoEnd Y coordinate (line only)
svgNoSVG content (for 'update')
textNoText content (text only)
colorNoText color hex code (text only)#000000
widthNoWidth in pixels (rectangle/ellipse only)
actionYesAction: 'list' (list drawings), 'create' (new drawing), 'update' (modify), 'delete' (remove), or 'batch' (create multiple)
formatNoOutput format: 'table' (default) or 'json' (for 'list')table
heightNoHeight in pixels (rectangle/ellipse only)
lockedNoLock/unlock drawing (for 'update')
drawingsNoList of drawing definitions (required for 'batch')
rotationNoRotation angle in degrees (for 'update')
font_sizeNoFont size in points (text only)
drawing_idNoDrawing ID (required for 'update' and 'delete')
fill_colorNoFill color hex code#ffffff
project_idNoProject ID (required for 'list')
font_familyNoFont family name (text only)TypeWriter
font_weightNoFont weight: 'normal' or 'bold' (text only)normal
border_colorNoBorder color hex code#000000
border_widthNoBorder width in pixels
drawing_typeNoShape type for 'create': 'rectangle' (box), 'ellipse' (circle/oval), 'line' (connector), 'text' (label)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Warns about the destructive nature of delete and mentions two-phase validation for batch. With empty annotations, the description carries the full burden and adequately discloses key behaviors, though permissions and side effects are omitted.

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?

Well-structured with a summary, actions list, return info, and examples. Front-loaded with purpose and no unnecessary text.

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 26 parameters and 5 actions, the description covers all actions with examples and mentions return format. Output schema exists for detailed returns, so this is adequate. Could be more explicit about required parameters per action, but schema handles that.

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 already has 100% coverage with descriptions. The description adds value through examples that demonstrate parameter combinations and usage patterns, which is beneficial for understanding.

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 'Manage drawings (CRUD operations)' and lists specific actions (list, create, update, delete, batch). This distinguishes the tool from unrelated siblings and covers all operations.

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?

Provides explicit actions and examples for when to use each action, making the usage context clear. However, it does not explicitly state when not to use or alternatives, though no competing tools exist.

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/ChistokhinSV/gns3-mcp'

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