Skip to main content
Glama
tigergraph

tigergraph-mcp

Official
by tigergraph
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tigergraph__get_edges

Read-onlyIdempotent

Fetch multiple graph edges from TigerGraph, with optional filtering by edge type or source vertex to explore relationships and support data analysis.

Instructions

Get multiple edges (relationships) from a TigerGraph graph, optionally filtered by type.

Use When: • Retrieving multiple edges • Exploring graph relationships • Data export and analysis

Quick Start:

{
  "source_vertex_type": "Person",
  "source_vertex_id": "user1",
  "edge_type": "FOLLOWS"
}

Tips: • Can filter by edge type • Returns all edges from a source vertex • Use 'get_neighbors' for simpler use cases

Related Tools: get_edge, get_neighbors, get_edge_count

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of edges to return.
profileNoConnection profile name. Omit to use the active default profile. Use 'list_connections' to see available profiles.
edge_typeNoType of the edge. If not provided, gets all types.
graph_nameNoName of the graph. If not provided, uses default connection.
source_vertex_idNoID of the source vertex. If not provided, gets all edges.
source_vertex_typeNoType of the source vertex. If not provided, gets all types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only nature is covered. The description adds that it 'Returns all edges from a source vertex' and can filter by edge type, which is useful behavioral context. But it doesn't disclose potential performance implications or pagination behavior, which would add value beyond the 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 sections ('Use When', 'Quick Start', 'Tips', 'Related Tools') and a code example. The core purpose is front-loaded in the first sentence, and every section adds value without redundancy. It is concise yet comprehensive.

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?

The description covers the main use cases, provides a quick start example, and lists related tools. Since there is no output schema, it would be helpful to describe the return format, but this is not critical for a read-only edge retrieval tool. The description is sufficiently complete for an agent to decide when to use it and how to invoke it with the given parameters.

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 all six parameters are already documented with descriptions. The description mentions filtering by edge type and returning all edges from a source vertex, which aligns with schema but adds no additional meaning beyond what the schema already provides. The baseline of 3 is appropriate.

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 'Get multiple edges (relationships) from a TigerGraph graph, optionally filtered by type.' It specifies the verb, resource, and context, and distinguishes itself from siblings like get_edge (singular) and get_neighbors by focusing on multiple edges and filtering.

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 description includes a 'Use When' section listing concrete scenarios (retrieving multiple edges, exploring graph relationships, data export and analysis) and a 'Tips' section recommending get_neighbors for simpler use cases. It also lists related tools. However, it doesn't explicitly state when NOT to use this tool beyond the suggestion of get_neighbors.

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