Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tigergraph__has_edge

Read-onlyIdempotent

Check if an edge exists between two vertices in TigerGraph. Returns a boolean, ideal for validation or avoiding duplicate edges before adding.

Instructions

Check if an edge (relationship) exists between two vertices without retrieving its data.

Use When: • Verifying relationship existence • Validation logic • More efficient than get_edge when you only need existence check

Quick Start:

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

Tips: • Returns boolean (true/false) • Faster than get_edge when you don't need the data • Use before add_edge to avoid duplicates

Related Tools: get_edge, add_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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds useful behavioral details: it returns a boolean, is faster than get_edge, and can be used pre-emptively before add_edge. No contradictions with annotations.

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 headers (Use When, Quick Start, Tips, Related Tools), front-loads the core purpose, and uses a compact JSON example. No redundant sentences; every section earns its place.

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 existence-check tool, the description covers purpose, usage guidance, return type, performance comparison, and related tools. With annotations providing the safety profile and no output schema needed (returns boolean), this is complete for an agent to decide when and how to call it.

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, so the baseline is 3. The description's Quick Start JSON example clarifies how the parameters map in practice (e.g., source_vertex_type as 'Person'), adding semantic value beyond the terse schema descriptions of each parameter.

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 ('Check if an edge exists') with a resource ('between two vertices') and explicitly notes it does so 'without retrieving its data,' which distinguishes it from get_edge. The purpose is unambiguous and distinct from sibling tools like get_edge and add_edge.

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 explicitly lists scenarios (verifying relationship existence, validation logic) and directly compares with get_edge ('more efficient... when you only need existence check'). It also advises using it before add_edge to avoid duplicates, providing clear routing to alternatives.

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