mindspark-mcp

Delete a MindSpark node

delete_node

Destructive

Delete a node and its entire subtree from a mind map. The root node cannot be deleted; delete the entire map instead.

Instructions

Delete a node and its entire subtree. Cannot delete the root node — delete the whole map instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mapId": "<mapId>",
      "nodeId": "<nodeId>"
    },
    "name": "delete_node"
  }
}

Input Schema

Name	Required	Description	Default
`mapId`	Yes
`nodeId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds critical behavioral details: the operation removes the entire subtree and is forbidden on the root node. This meaningfully expands on the raw annotation flags.

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?

The description is a single, focused sentence that front-loads the action and scope, then adds a necessary constraint and alternative. No filler or redundant 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?

The description covers the core behavior, the key exception, and the fallback tool, which is sufficient for a simple delete operation. It does not elaborate on parameter meanings, but the names are reasonably self-explanatory in the MindSpark context, and no output schema is expected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides only names and types for mapId and nodeId, with no descriptions or titles. The description does not explain these parameters, leaving their exact meaning and format implicit. Since schema coverage is low and the description fails to compensate, parameter semantics are under-specified.

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 action (Delete) and the object (a node and its entire subtree), immediately distinguishing this tool from sibling tools like delete_map. The explicit note about the root node restriction further clarifies its scope.

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?

The description provides an explicit when-not-to-use condition ('Cannot delete the root node') and directs the user to the alternative ('delete the whole map instead'). This gives clear guidance on when to choose this tool over a sibling.

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

Deploy Server