Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph

tigergraph__add_node

Idempotent

Add a single vertex to a TigerGraph graph, creating it if absent or updating its attributes if present. Use for inserting individual entities like users, products, or documents.

Instructions

Add a single node (vertex) to a TigerGraph graph. This performs an upsert operation - creates a new vertex if it doesn't exist, or updates attributes if it does.

Use When: • Creating a single new entity (user, product, document, etc.) • Updating an existing vertex's attributes • You have individual entities to add (not batch loading)

Quick Start:

{
  "vertex_type": "Person",
  "vertex_id": "user123",
  "attributes": {"name": "Alice", "age": 30}
}

Common Workflow:

  1. Call 'show_graph_details' to understand vertex types and attributes

  2. Use 'add_node' to create individual vertices

  3. Call 'get_node' to verify the vertex was created

  4. Use 'add_edge' to connect this vertex to others

Tips: • For multiple vertices: Use 'add_nodes' instead (more efficient) • Primary key is required (usually the 'id' attribute) • Attribute names must match the schema exactly (case-sensitive) • This is an upsert: existing vertices are updated, not duplicated

More Examples:

// Add a product
{
  "vertex_type": "Product",
  "vertex_id": "prod456",
  "attributes": {"name": "Laptop", "price": 999.99, "category": "Electronics"}
}

// Add a document with minimal attributes
{
  "vertex_type": "Document",
  "vertex_id": "doc789",
  "attributes": {"title": "Report Q4 2024"}
}

Related Tools: • add_nodes - Batch insert multiple vertices • get_node - Retrieve a vertex by ID • delete_node - Remove a vertex • has_node - Check if vertex exists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoConnection profile name. Omit to use the active default profile. Use 'list_connections' to see available profiles.
vertex_idYesID of the vertex (primary key value). Format: String or integer depending on schema. Example: 'user123', 'product_456', or 12345 Note: Must be unique within the vertex type.
attributesNoVertex attributes as key-value pairs. Keys must match the vertex type schema. Values should match the expected data types. Example: {'name': 'Alice', 'age': 30, 'email': 'alice@example.com'} Tip: Use 'show_graph_details' to see required attributes and types.
graph_nameNoName of the graph. If not provided, uses the default connection. Tip: Use 'list_graphs' to see available graphs.
vertex_typeYesType of the vertex (must exist in graph schema). Example: 'Person', 'Product', 'Company' Tip: Use 'show_graph_details' to see available vertex types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.5/5.0
Behavior4/5

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

The description goes beyond the annotations by revealing the upsert behavior, stating that existing vertices are updated rather than duplicated, and emphasizing exact schema matching. However, it does not clarify whether omitted attributes are preserved or overwritten on an update, which is important for a mutation tool that can modify existing data. This is the main transparency gap.

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 well-structured with clear headings, code examples, and a front-loaded purpose statement. It is longer than strictly necessary, with some redundancy between the 'Use When' bullets and the 'Tips' section, but every major section still serves a useful role for a complex graph 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?

For a 5-parameter mutation tool with no output schema, the description supplies a discovery workflow, practical examples, and routing to verification via get_node. It does not describe return values or failure behavior on schema violations, but the included workflow compensates sufficiently for a tool of this complexity.

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 100%, so the baseline is 3, but the description adds a full quick-start payload and concrete examples that show how vertex_type, vertex_id, and attributes fit together. The tips about the primary key requirement and case-sensitive attribute names also add practical meaning beyond the schema, though the schema already handles most parameter documentation.

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 first sentence states a specific verb and resource: 'Add a single node (vertex) to a TigerGraph graph.' It immediately clarifies the upsert semantics and explicitly contrasts with batch loading, distinguishing it from sibling tools like add_nodes. An agent can tell exactly what this tool does without opening the 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?

The 'Use When' section gives clear criteria for single-entity creation or update, and the tips explicitly say to use add_nodes for multiple vertices. The 'Common Workflow' and 'Related Tools' sections further guide the agent to show_graph_details, verify with get_node, and connect with add_edge, leaving little ambiguity about when and how to use this tool.

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