Skip to main content
Glama

trident

by io.github.alexeibespalov

update_node

Idempotent

Updates properties of an existing node in a live Trident document. Only the fields you provide are changed; others are preserved. Use get_document_summary to get all node IDs before calling this. Requires a valid editor access token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesEditor access token for this document. The document ID is embedded in the token.
nodeIdYesID of the node to update
agentIdYesYOUR AI assistant name (e.g. "Claude.ai", "GitHub Copilot"). Shown as "[agentId] working with [userName]" in the collaboration presence dot.
changesYesFields to update. Only provided fields are changed.
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.

TDQS

A4.2/5.0
Behavior4/5

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

Adds key behavior beyond annotations: partial-update semantics ('Only the fields you provide are changed; others are preserved') and auth requirement ('Requires a valid editor access token'). Annotations already cover readOnly/destructive hints, so description enriches context.

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 concise sentences each add value: purpose, partial-update behavior, and prerequisite/auth. No fluff.

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?

For a moderate-complexity tool with a nested changes object and no output schema, the description covers core usage, precondition, and auth. It doesn't explain failure behavior or return values, but with annotations and schema, this is adequate.

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%, so baseline 3. The description adds a small hint about obtaining nodeId via get_document_summary, but most parameter meaning is already in the schema; no significant extra semantics.

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?

Clearly states a specific verb ('Updates'), resource ('properties of an existing node'), and context ('live Trident document'). Distinguishes from siblings like add_node, update_annotation, and update_container by specifying node.

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?

Provides a clear prerequisite ('Use get_document_summary to get all node IDs') but does not explicitly contrast with alternatives like update_annotation or update_container. The context implies usage for existing node property updates.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: CRUD operations for nodes, containers, connections, and annotations are separated, and read-only/utility tools like open_document, get_document_summary, and explain are well-differentiated. No two tools have overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g. add_node, delete_connection, get_document_summary). Even utility tools like open_document and validate_trident adhere to this pattern, making the set predictable and easy to navigate.

Tool Count4/5

With 22 tools, the server is slightly above the typical well-scoped range (3-15). Each tool serves a specific purpose, covering CRUD for diagram elements, multiple read operations, and collaboration features, but the count feels a bit heavy for a focused diagramming tool.

Completeness4/5

The tool set provides comprehensive CRUD for core elements (nodes, containers, connections, annotations), multiple read methods, guides, and collaboration aids. Minor gaps exist: no bulk operations, no tool to create or manage documents themselves, but the core editing workflow is well-covered.

Resources