Neo4j Schema Query Builder
pip install llama-index-tools-neo4j
The Neo4jQueryToolSpec class provides a way to query a Neo4j graph database based on a provided schema definition. The class uses a language model to generate Cypher queries from user questions and has the capability to recover from Cypher syntax errors through a self-healing mechanism.
Table of Contents
Usage
Initialization
Initialize the Neo4jQueryToolSpec class with:
from llama_index.tools.neo4j import Neo4jQueryToolSpec
from llama_index.llms.openai import OpenAI
from llama_index.core.agent.workflow import FunctionAgent
gds_db = Neo4jQueryToolSpec(
url="neo4j-url",
user="neo4j-user",
password="neo4j=password",
llm=llm,
database="neo4j",
)
tools = gds_db.to_tool_list()
agent = FunctionAgent(
tools=tools,
llm=OpenAI(model="gpt-4.1"),
)
Where:
url: Connection string for the Neo4j database.user: Username for the Neo4j database.password: Password for the Neo4j database.llm: A language model for generating Cypher queries (any type of LLM).database: The database name.
Running a Query
To use the agent:
# use agent
resp = await agent.run("Where is JFK airport is located?")
Generated Cypher:
MATCH (p:Port {port_code: 'JFK'})
RETURN p.location_name_wo_diacritics AS Location
Final answer:
'The port code JFK is located in New York, United States.'
Features
- Schema-Based Querying: The class extracts the Neo4j database schema to guide the Cypher query generation.
- Self-Healing: On a Cypher syntax error, the class corrects itself to produce a valid query.
- Language Model Integration: Uses a language model for natural and accurate Cypher query generation.
Metadata
Release files for llama-index-tools-neo4j 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| llama_index_tools_neo4j-0.6.0.tar.gz | 7.3 kB | Without provenance | Details for llama_index_tools_neo4j-0.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| llama_index_tools_neo4j-0.6.0-py3-none-any.whl | Python 3 | none | any | Details for llama_index_tools_neo4j-0.6.0-py3-none-any.whl |
Total release size: 14.4 kB
Release files / llama_index_tools_neo4j-0.6.0.tar.gz
| Download URL | llama_index_tools_neo4j-0.6.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49f98bd9f42a2a8504bc99cbeae8dd489623fe114149abeedcb39106c4192c89
|
|
BLAKE2b-256 checksum How to use checksums |
74449603c3c9adfd74822155acafdf19b8bee956196ae9bfa62437b2f61c4301
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.7 {"installer":{"name":"uv","version":"0.12.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / llama_index_tools_neo4j-0.6.0-py3-none-any.whl
| Download URL | llama_index_tools_neo4j-0.6.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ad9b3021006f1028ff65140558a56405d3b4bd442b017163f749534220c2cdd
|
|
BLAKE2b-256 checksum How to use checksums |
8412959e680eea9a5cce001730875cef18f412a1b6de3f502436680ee4437d01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.7 {"installer":{"name":"uv","version":"0.12.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for llama-index-tools-neo4j 0.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.