Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph

tigergraph__get_node_edges

Retrieve all outgoing edges from a specified vertex, with optional filtering by edge type. Returns edge details including type, attributes, and target vertex information.

Instructions

Purpose: Retrieve all edges connected to a specific vertex (node).

When to Use:

  • Explore connections from a vertex

  • Find relationships of a specific type

  • Analyze node connectivity patterns

  • Get edge attributes and target vertices

What You Get:

  • Edge type and ID

  • Edge attributes

  • Target vertex information

  • Edge direction (outgoing from the specified vertex)

Common Workflows:

  1. Explore all connections: get_node_edges(vertex_type='Person', vertex_id='123')

  2. Specific relationship type: get_node_edges(..., edge_type='FRIEND_OF')

  3. Degree analysis: Count returned edges to get outgoing degree

Tips:

  • Returns OUTGOING edges only (edges starting from this vertex)

  • Use get_node_degree() for quick connection count

  • Use get_neighbors() to get target vertices without edge details

  • Combine with pagination (limit) for highly connected vertices

Note: This returns edges where the specified vertex is the SOURCE. For incoming edges, use a reverse traversal query or get_neighbors().

Related Tools:

  • get_node_degree: Count connections without retrieving edges

  • get_neighbors: Get connected vertices

  • get_edges: Query edges by type across the graph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of edges to return (default: 100)
profileNoConnection profile name. Omit to use the active default profile. Use 'list_connections' to see available profiles.
edge_typeNoOptional: Filter by specific edge type. If omitted, returns all edge types.
vertex_idYesThe unique identifier of the source vertex
graph_nameNoName of the graph (uses default if not specified)
vertex_typeYesThe type of the source vertex

Schema Changelog

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

  1. First observedv1.0.2

TDQS

A5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It transparently explains that only outgoing edges are returned, what edge and target information is included, and how the profile and limit parameters behave.

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, bullet points, examples, and related-tool references. Each sentence serves a distinct informative purpose without unnecessary repetition.

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?

Despite having no output schema, the description clearly states what the caller should expect: edge type and ID, edge attributes, target vertex information, and edge direction. It also covers common workflows, tips, and relationship to sibling tools, making it complete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has 100% parameter description coverage, and the tool description adds further semantic value with concrete examples and tips. It clarifies the meaning of edge_type filtering, vertex identification, and the role of limit.

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 clearly states the tool retrieves all edges connected to a specific vertex, using a specific verb and resource. It also explicitly distinguishes this tool from siblings by noting it returns outgoing edges only.

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 provides explicit when-to-use guidance, common workflows, and examples. It clearly contrasts with related tools such as get_node_degree, get_neighbors, and get_edges, making the selection criteria unambiguous.

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