Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tigergraph__delete_edge

DestructiveIdempotent

Delete a specific edge between two vertices to remove a relationship or disconnect them. Specify source, edge type, and target to permanently delete the edge while keeping the vertices.

Instructions

Delete a single edge (relationship) from a TigerGraph graph.

Use When: • Removing a specific relationship • Disconnecting two vertices • Graph maintenance

Quick Start:

{
  "source_vertex_type": "Person",
  "source_vertex_id": "user1",
  "edge_type": "FOLLOWS",
  "target_vertex_type": "Person",
  "target_vertex_id": "user2"
}

Warning: • Operation is permanent • Does not delete the vertices, only the edge

Related Tools: delete_edges, add_edge, has_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.
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.1/5.0
Behavior4/5

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

Annotations already mark the operation destructive, read-write, and idempotent. The description adds value by warning that the operation is permanent and clarifying that it deletes only the edge, not the connected vertices. This goes beyond the annotation flags without contradicting them.

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 Use When, Quick Start, Warning, and Related Tools sections, and the main action is front-loaded. The content is mostly purposeful, though the 'Graph maintenance' bullet is slightly generic and the Quick Start block adds length without being strictly necessary.

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 straightforward single-edge delete, the description covers the effect, permanence, scope, and required arguments via the example. It does not specify behavior when the edge does not exist or describe the response/return value, but given the simple operation and strong schema/annotations, these are minor gaps.

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 description coverage is 100%, so the schema already documents all seven parameters. The description contributes a Quick Start JSON example showing how the five required parameters fit together, but it does not add deeper meaning about profile, graph_name, or vertex ID semantics 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?

The opening sentence names a specific verb ('Delete'), a specific resource ('edge'), and a scope qualifier ('single') that distinguishes it from sibling tools like delete_edges. The Related Tools line reinforces the distinction by naming delete_edges, add_edge, and has_edge.

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?

The 'Use When' section gives concrete scenarios such as removing a specific relationship or disconnecting two vertices. It does not explicitly state when to prefer delete_edges or has_edge, but the 'single edge' qualifier and Related Tools list make the intended context reasonably clear.

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