Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph

tigergraph__add_edge

Adds an edge between two existing vertices in a TigerGraph graph, with optional edge attributes.

Instructions

Add a single edge (relationship) to a TigerGraph graph connecting two vertices.

Use When: • Creating a relationship between two entities • Connecting vertices in the graph • Building graph structure • Adding individual relationships

Quick Start:

{
  "source_vertex_type": "Person",
  "source_vertex_id": "user1",
  "edge_type": "FOLLOWS",
  "target_vertex_type": "Person",
  "target_vertex_id": "user2",
  "attributes": {"since": "2024-01-15"}
}

Common Workflow:

  1. Ensure both source and target vertices exist (use 'add_node')

  2. Call 'add_edge' to create relationship

  3. Optionally add edge attributes (like timestamps)

  4. Verify with 'get_neighbors' or 'get_node_edges'

Tips: • Both vertices must exist before adding edge • Edge type must match schema definition • For multiple edges, use 'add_edges' (more efficient) • Edge attributes are optional

Related Tools: add_edges, add_node, get_neighbors, delete_edge

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoConnection profile name. Omit to use the active default profile. Use 'list_connections' to see available profiles.
edge_typeYesType of the edge.
attributesNoEdge attributes. Example: {'weight': 0.5, 'date': '2023-01-01'}
graph_nameNoName of the graph. If not provided, uses default connection.
source_vertex_idYesID of the source vertex.
target_vertex_idYesID of the target vertex.
source_vertex_typeYesType of the source vertex.
target_vertex_typeYesType of the target vertex.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.2

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses key preconditions (both vertices must exist, edge type must match schema) and notes that attributes are optional. Does not explicitly mention error behavior on duplicates or failure, hence not a 5.

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?

Well-structured with clear sections (Use When, Quick Start, Common Workflow, Tips, Related Tools). Every sentence adds value; no fluff or redundancy.

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 an 8-parameter operation, the description provides all necessary context: prerequisites, workflow, optional parameters, and references to related tools. No critical information is missing for an agent to invoke it correctly.

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 covers 100% of parameters with descriptions, so baseline is 3. The description adds a complete quick-start example, explains the optional attributes, and provides workflow context that clarifies parameter usage beyond the schema.

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 it adds a single edge connecting two vertices, distinguishes from add_edges for bulk operations, and lists related tools. No ambiguity about the resource or verb.

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?

Provides explicit 'Use When' conditions, a common workflow with verification steps, and tips about prerequisites and when to use add_edges instead. Fully guides an agent on when to select this tool over alternatives.

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/tigergraph/tigergraph-mcp'

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