Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Remove node

node_remove
Destructive

Deletes a node and its outgoing links plus links from other nodes, updating the .illugen project in place. Irreversible; copy the file first or use node_set(disabled=true) to bypass it.

Instructions

Deletes a node from the graph, with its outgoing links and every link from other nodes into it.

Writes the project file in place and cannot be undone: copy the file first if you may need the node back.
To bypass a node without losing it, use node_set(disabled=true) instead.
Returns: removed_links, the number of links from other nodes that pointed to the deleted node.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of the .illugen project file.
graphNoGraph to work in: empty for the top-level graph, or the id or label of a Node_Subgraph node ('outer/inner' for nested subgraphs).
node_idYesNode id as a string (from project_summary or node_add), or the node's label if it is unique.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / graph / description
      Added value: +"Graph to work in: empty for the top-level graph, or the id or label of a Node_Subgraph node ('outer/inner' for nested subgraphs)."
    • addedInput schema / properties / node_id / description
      Added value: +"Node id as a string (from project_summary or node_add), or the node's label if it is unique."
    • addedInput schema / properties / path / description
      Added value: +"Absolute path of the .illugen project file."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes further: it discloses that the project file is written in place, that the operation cannot be undone, that incoming links are cascade-deleted, and what the return value contains. This is exactly the extra context an agent needs before an irreversible mutation.

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, each with a distinct job: what it does and cascades, the irreversibility warning and alternative, then the return value. Front-loaded with the core action, zero filler.

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 output schema, the description carries the return-value burden itself ('removed_links, the number of links from other nodes that pointed to the deleted node') and covers the destructive nature. Nothing an agent needs to invoke this safely is 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 description coverage is 100%, so path, graph, and node_id are already fully documented in the schema. The description refers to the node generically but adds no syntax, format, or edge-case meaning beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (Deletes) plus the exact resource (a node from the graph) and the full blast radius (its outgoing links and every incoming link). This scope statement distinguishes it from siblings like link_remove and node_set without needing to open any schema.

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 routes the agent to an alternative ('To bypass a node without losing it, use node_set(disabled=true) instead') and gives a concrete prerequisite (copy the file first if you may need the node back). Both when-to-use and when-not-to-use are covered.

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

Deploy Server

Other Tools