Skip to main content
Glama

modify_diagram

Modify existing Excalidraw architecture diagrams by adding, removing, or updating nodes and connections without recreating the diagram.

Instructions

Modify an existing Excalidraw diagram created by this tool.

Supports iterative editing: add components, remove nodes, update labels, and rewire connections - without recreating the entire diagram.

IMPORTANT: Call get_diagram_info first to understand the current diagram state before making modifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the existing .excalidraw file.
operationsYesOrdered list of operations. Each dict has: - op: "add_node" | "remove_node" | "update_node" | "add_connection" | "remove_connection" For add_node: - id (str): New node identifier - label (str): Display text - component_type (str, optional): Technology for auto-styling - shape (str, optional): Shape override - color (str, optional): Hex color override - planned (bool, optional): Mark as planned/future (dashed + 60% opacity) - near (str, optional): Place near this existing node id For remove_node: - id (str): Node to remove (also removes its connections) For update_node: - id (str): Node to update - label (str, optional): New label - component_type (str, optional): New component type - color (str, optional): New hex color (pass empty string to clear) - planned (bool, optional): Toggle planned state For add_connection: - from_id (str): Source node id - to_id (str): Target node id - label (str, optional): Edge label For remove_connection: - from_id (str): Source node id - to_id (str): Target node id
themeNoColor theme for re-rendering. Default: "default"default

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Discloses it modifies (not creates), supports iterative edits, and warns to check current state. However, with no annotations, it misses details on atomicity, partial failures, or side effects of operations.

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?

Three short paragraphs: purpose, capabilities, and a critical warning. No redundant wording, front-loaded with key information.

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?

Covers the tool's purpose, iterative nature, and prerequisite call. With an output schema present, return value explanation is not needed, but error handling or operation ordering constraints are missing.

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?

Schema coverage is 100% with detailed descriptions of each operation's parameters. Description adds context about iterative editing but does not supplement parameter meaning beyond 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?

Description clearly states the tool modifies existing Excalidraw diagrams and distinguishes it from siblings like create_diagram by specifying 'modify an existing' and 'without recreating the entire diagram'.

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?

Explicitly instructs to call get_diagram_info first to understand current state before modifications. Lacks explicit when-not-to-use guidance but the prerequisite is clear.

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/KTCrisis/arch7'

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