Skip to main content
Glama

trident

by io.github.alexeibespalov
OverviewDiscussionsAdmin

add_node

Adds a new node (entity) to a live Trident document. The node appears immediately for all collaborators. Requires a valid editor access token. Before adding nodes: call open_document to understand the diagram layout and pick sensible positions; call get_document_summary to get all existing entity IDs so you can avoid duplicates. IMPORTANT: if this node belongs inside a container, pass node.container on THIS call — do NOT create the node without a container and reparent it later via update_node. Orphaned nodes appear immediately to all live collaborators and create unnecessary visual churn.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesNode definition
tokenYesEditor access token for this document. The document ID is embedded in the token.
agentIdYesYOUR AI assistant name (e.g. "Claude.ai", "GitHub Copilot"). Shown as "[agentId] working with [userName]" in the collaboration presence dot.
userNameNoFirst name of the human you are assisting (ask them at session start if you do not know). Shown in the collaboration presence dot as "[agentId] working with [userName]".
action_explanationNoOptional: brief explanation of what this action does and why (max 250 chars). Shown live to human collaborators in the AI cursor tooltip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / node / properties / shapeType / description
      Previous value: -"Optional: shape type, e.g. \"diamond\", \"rectangle\""New value: +"Optional: shape type. Default \"rectangle\"; \"diamond\" for decisions. Registered collections: Flowchart (\"flowchart-process\", \"flowchart-rounded\", \"flowchart-stadium\", \"flowchart-cylinder\", \"flowchart-circle\", \"flowchart-double-circle\", \"flowchart-decision\", \"flowchart-hexagon\", \"flowchart-parallelogram\", \"flowchart-trapezoid\", etc.), BPMN (\"bpmn-start-event\", \"bpmn-end-event\", \"bpmn-gateway\", \"bpmn-task\", \"bpmn-user-task\", \"bpmn-subprocess\", etc.; labels render under events/gateways), UML (\"uml-class\", \"uml-interface\", \"uml-package\", \"uml-component\", \"uml-database\", \"uml-actor\", \"uml-state\", \"uml-action\", etc.), General primitives (\"circle\", \"cylinder\", \"hexagon\", \"rounded-rect\", \"parallelogram\", \"trapezoid\", etc.), or Organic (\"cloud\", \"star\", \"heart\", etc.). Unknown values fall back to rectangle."
  2. Changed3 schema fields changed
    • addedInput schema / properties / node / properties / color
      Added value: +{
+  "description": "Optional: background/fill color (hex like \"#438DD5\" or a color name). Set on THIS call — do not add the node and recolor it later with update_node.",
+  "type": "string"
+}
    • addedInput schema / properties / node / properties / outlineColor
      Added value: +{
+  "description": "Optional: border/outline color (hex or color name).",
+  "type": "string"
+}
    • addedInput schema / properties / node / properties / textColor
      Added value: +{
+  "description": "Optional: label text color (hex or color name), e.g. \"#FFFFFF\".",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / node / properties / container / description
      Previous value: -"Optional: ID of a container to place this node inside"New value: +"ID of the container this node belongs in. Set this NOW if you know the parent — do not create the node orphaned and reparent later with update_node. Treat this as required whenever the node has a logical parent container."
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=false, openWorldHint=true, and idempotentHint=false, and the description complements that by adding important behavioral context: the node appears immediately for all collaborators, a valid editor access token is required, and orphaned nodes create visual churn. These traits are not inferable from the schema alone and materially affect how the agent should plan the call.

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 concise, front-loaded with the core action and immediate effect, and then provides sequential guidance and an IMPORTANT container-specific warning. Every sentence adds operational value without repetition or 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?

For a live collaborative mutation tool with a nested node schema and no output schema, the description covers the essential operational context: prerequisites, immediate visibility, token requirement, duplicate avoidance, and the container pitfall. Nothing critical for invoking the tool correctly is missing.

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 description coverage is 100%, so parameters are already well documented. The description adds value beyond the schema by explaining that node.id must be unique (avoid via get_document_summary) and that node positions should be informed by open_document. It does not enumerate parameters, but the schema already does that thoroughly.

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 starts with a specific verb and resource: 'Adds a new node (entity) to a live Trident document.' It clearly distinguishes this from sibling tools like add_connection, add_container, and update_node by focusing on node creation and explicitly warning against the update_node reparenting path.

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 gives explicit when-to-use guidance: call open_document before adding to understand layout, and call get_document_summary to avoid duplicate IDs. It also states what not to do: do not create a node without its container and reparent later via update_node. This is actionable and prevents a common misuse.

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

All trident toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources