Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tigergraph__add_edge

Idempotent

Create a relationship between two vertices by adding a single edge to a TigerGraph graph. Specify source, target, and edge type to connect entities.

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.

  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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds valuable context such as the requirement that both vertices must exist, the edge type must match the schema, and that attributes are optional. It does not contradict the annotations, and the additional tips go beyond what annotations provide.

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 well-structured with clear sections (Use When, Quick Start, Common Workflow, Tips, Related Tools). Every section is informative and earns its place; it is appropriately detailed without being verbose.

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 simple mutation tool with no output schema, the description covers the essential context: what the tool does, when to use it, prerequisites, workflow, alternatives, and verification steps. Nothing an agent needs to call it 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?

The input schema has 100% description coverage for all parameters. The description adds a quick-start JSON example that shows how parameters combine, and explicitly notes that attributes are optional, adding semantic value beyond the schema's per-field descriptions.

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 states precisely that the tool adds a single edge connecting two vertices, and the 'Use When' section gives concrete scenarios. It clearly distinguishes from add_edges (multiple edges) and related tools, making the purpose unambiguous.

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 explicitly lists when to use the tool, provides a step-by-step workflow, and names the alternative add_edges for batch operations. It also states prerequisites (vertices must exist) and how to verify the result with get_neighbors/get_node_edges, leaving no ambiguity about usage.

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