Skip to main content
Glama
Sebastien-VZN

axomind-mcp

by Sebastien-VZN
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

add_nodes

Append new nodes to an existing mindmap using a simplified JSON format. Ideal for incremental updates to mindmap structures.

Instructions

Append nodes to an existing mindmap (simplified format).

Unlike sync_nodes which replaces everything, add_nodes reads the existing mindmap, appends the new nodes, and syncs the full set.

Simplified node format (JSON string): [ {"title": "Node 1", "parent": 0, "color": "0xFF7A8FF5"}, {"title": "Node 2", "parent": 1, "color": "0xFFFF6F91"}, {"title": "Node 3", "parent": 1} ]

Fields:

  • title (required): node title

  • parent (required): order_index of the parent node (0 = root)

  • color (optional): hex color (default: 0xFF7A8FF5)

  • pos_x, pos_y (optional): canvas position (default: 0)

  • size_box (optional): 0=normal, 1=category, 2=root

  • bold, italic, underline (optional): text style

  • line_type (optional): 0=curve, 1=rounded, 2=square

  • line_style (optional): 0=solid, 1=dashed

  • stroke_width, dot_radius, radius, border_size, label_size (optional)

  • icon_id (optional): icon ID

  • active_bg_colors (optional): active background colors

  • descriptions (optional): descriptive text

  • free_links (optional): list of order_index for free links. ONLY use to close a cycle (e.g. topology A→B→C→A). Do NOT use in pure tree structures (file trees, doc trees, org charts). One free_link per cycle max.

  • spacing_h (optional): horizontal spacing multiplier 0-10 (default: 1). 0=1 cell gap (60px), 1=2 cells (120px), etc.

  • spacing_v (optional): vertical spacing multiplier 0-10 (default: 0)

  • is_write_children (optional): propagate style to children (default: false)

Auto-positioning: when free_links are present, new nodes are auto-positioned using a hierarchical tree layout (retrospective mode). When no free_links, positions stay at default (0,0) and the Flutter client handles layout.

UID and order_index are assigned automatically after existing nodes. All other fields are filled with application defaults.

Args: id_mindmap: Mindmap ID nodes: JSON string — array of simplified nodes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodesYes
id_mindmapYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

With no annotations, the description discloses key behaviors: appending vs replacing, auto-positioning with free_links, auto-assignment of UID/order_index, and default values. It does not mention rate limits or auth, but for a mutation tool this is sufficient.

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 lengthy but well-structured: purpose sentence, sibling contrast, format, field details, and behavioral notes. It front-loads the key purpose and contrast. Some redundancy exists (e.g., 'append nodes' repeated), but overall it is efficiently organized for a complex tool.

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 the tool has an output schema (not shown), return value explanation is unnecessary. The description covers parameter details, auto-assignment, positioning behavior, and free_link constraints. The id_mindmap parameter could use slightly more context, but the overall completeness for a 2-param tool is good.

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 coverage is 0%, so the description compensates with extensive detail on the nodes parameter: full field list, defaults, constraints on free_links, and positional behavior. The id_mindmap parameter is minimally described as 'Mindmap ID', but that is acceptable for an integer ID.

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 'Append nodes to an existing mindmap (simplified format)' and explicitly contrasts with sync_nodes, which replaces everything. This provides a specific verb+resource and distinguishes it from a sibling tool.

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 contrasts add_nodes with sync_nodes, explaining when to use each. It also provides guidance on free_links usage (only for cycles, not pure trees). While it does not explicitly list when not to use, the contrast and field notes offer adequate context.

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/Sebastien-VZN/axomind-mcp'

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