Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tigergraph__get_edge

Read-onlyIdempotent

Retrieve a specific edge from a TigerGraph graph by providing its source vertex, target vertex, and edge type. Use it to check edge attributes or verify that a relationship exists.

Instructions

Get a single edge (relationship) from a TigerGraph graph by specifying source, target, and edge type.

Use When: • Retrieving a specific relationship • Checking edge attributes • Verifying edge was created

Quick Start:

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

Tips: • Requires full edge specification (source, target, type) • Returns edge attributes if any • Use 'get_neighbors' for simpler neighbor queries

Related Tools: get_edges, has_edge, get_neighbors

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.4/5.0
Behavior4/5

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

Annotations already declare this tool read-only, idempotent, and non-destructive. The description adds useful behavioral detail: it requires full edge specification, returns edge attributes if any, and routes simpler queries to get_neighbors. It does not detail not-found or error behavior, but the annotations cover the safety profile.

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-organized into scannable sections: summary, Use When, Quick Start, Tips, and Related Tools. It is front-loaded with the core purpose and every section adds distinct value without redundancy.

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 single-edge read with read-only annotations and full schema coverage, the description covers purpose, required parameters, usage context, return behavior, and alternatives. A fuller explanation of the exact return shape or not-found behavior would help, but the tool is safe to invoke based on the provided details.

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 parameters are already documented in the schema. The Quick Start example and the tip 'Requires full edge specification' add integration-level meaning by showing how the required parameters combine, which raises it above the baseline.

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 operation: retrieving a single edge by source, target, and edge type. The description clearly names the resource and criteria, and the Related Tools section distinguishes it from get_edges, has_edge, and get_neighbors.

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: retrieving a specific relationship, checking edge attributes, and verifying edge creation. It also names an alternative tool, get_neighbors, for simpler queries, though it does not fully spell out when to prefer get_edges or has_edge over 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