Skip to main content
Glama
GrafeoDB

grafeo-mcp

Official
by GrafeoDB

vector_graph_search

Performs semantic vector search, then expands each result's graph neighborhood to reveal contextual relationships.

Instructions

Hybrid search: find similar nodes by vector, then expand their graph neighborhood.

This is the most powerful search tool — it combines semantic similarity (vector search) with graph structure (neighbor expansion). Use it when you want to find relevant nodes AND understand their context.

Step 1: Vector search finds the top-k most similar nodes. Step 2: For each result, expands outward by expand_depth hops.

Use this tool when: you need both semantic relevance AND graph context. Use vector_search when: you only need the similar nodes themselves. Use get_neighbors when: you already have a node and want to explore around it.

Args: label: Node label to search (must have a vector index). property: Property holding the embedding vector. query_vector: The query embedding as a list of floats. k: Number of nearest seed nodes to return (default 5). expand_depth: How many hops to expand from each seed (default 1). Use 0 to skip expansion (equivalent to plain vector_search). expand_edge_type: Optional edge type filter. If provided, only edges of this type are followed during expansion.

Returns: JSON object with "seeds" (vector results) and "neighbors" (expanded context), truncated if the output is large.

Example call: vector_graph_search("Article", "embedding", [0.1, ...], k=3, expand_depth=2, expand_edge_type="CITES")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYes
propertyYes
query_vectorYes
kNo
expand_depthNo
expand_edge_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden. It explains the two-step process (vector search then expansion), defaults, and optional edge filtering. It mentions output truncation. However, it does not discuss potential performance implications or authentication needs.

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 clear sections, step-by-step explanation, and an example. It is moderately long but every sentence adds value, and the structure aids readability. Slightly verbose but justified for a complex tool.

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?

Given the tool's complexity (6 parameters, hybrid search) and the presence of an output schema, the description is complete. It explains the multi-step process, parameter defaults, return structure ('seeds' and 'neighbors'), and includes an example. No gaps.

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 description coverage is 0%, so the description must compensate. It adds meaning: label must have a vector index, query_vector is a list of floats, expand_depth can be 0 to skip expansion. The example clarifies usage. Some parameters (property, k) are briefly described but could include more nuance.

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's purpose as hybrid search combining vector similarity and graph expansion. It explicitly distinguishes from sibling tools like vector_search and get_neighbors, making it easy for an AI agent to select the right tool.

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 guidance on when to use this tool versus alternatives: 'Use this tool when: you need both semantic relevance AND graph context. Use vector_search when: you only need the similar nodes themselves. Use get_neighbors when: you already have a node and want to explore around it.'

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/GrafeoDB/grafeo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server