# Graph Query Advisory Session (30 min) with Lonnie VanZandt

> Graph Query Construction — Apache TinkerPop Gremlin and Neo4j Cypher. Whether you're writing your first traversal or staring at one that has been running for twenty minutes, this is time to think it through with someone who has been there. Graph databases are the right home for richly related, unstructured business information — the real instances of things and how they actually connect. That's a different job from OWL and SPARQL, which shine at describing how concepts relate. But writing a good graph query is an art, not a recipe for joining tables. A well-shaped traversal returns in milliseconds; a poorly shaped one runs for tens of minutes, or never finishes at all — and the difference is rarely obvious from the query text alone. I've spent years working as a graph query analyst in both Gremlin and Cypher, with tools like G.dot.V for TinkerPop. Bring me the traversal you can't make fast, or the one you can't make work, and we'll diagnose it together: where it's fanning out, where an index isn't being used, where the shape of the data is fighting the shape of the question. And if you want to see graph databases working inside MCP servers, thebrain-mcp (https://github.com/lonniev/thebrain-mcp) and cypher-mcp (https://github.com/lonniev/cypher-mcp) are live examples of exactly that — the latter serving parameterized, named Cypher templates as priced answers rather than raw database access. Think of it as an Opinion Shop rather than a Repair Shop. I'm not here to take the problem off your hands for weeks — I'm here to sit with it beside you. Free AI will hand you endless how-to, and a long retainer will hand you someone to do the work, but what's genuinely hard to find is an unhurried, honest conversation with another person who has walked this road. Someone to hear you out, reflect back what I'm seeing, and help you trust your own judgment again. Building alone means most of these decisions happen quietly in your own head; this is your chance to make one of them out loud. And when you need it, I'll be the audience that helps you pressure-test a pitch before it counts. Who am I to weigh in? I'm Lonnie VanZandt — Prime Authority of the Tollbooth DPYC™ ecosystem, with nearly 40 years building integrated IT systems. Background and full CV: https://htmlpreview.github.io/?https://raw.githubusercontent.com/lonniev/dpyc-community/refs/heads/main/docs/founder/LonnieVanZandt_2026.html And if you come away feeling it wasn't worth your time, just say so and I'll refund it.

- Host: Lonnie VanZandt
- Duration: 30 min
- Location: Cal Video, Google Meet, +17202011349
- Host time zone: America/New_York
- Confirmation: Bookings are confirmed instantly.
- Payment: required, and collected on the booking page.
- Booking page: https://cal.com/lonnie-vanzandt-dpyc/graph-query-advisory-30
- Event type id: 6292747

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=6292747&start=YYYY-MM-DD&end=YYYY-MM-DD&timeZone=<IANA time zone>
cal-api-version: 2024-09-04
```

The response is `{"data":{"YYYY-MM-DD":[{"start":"<ISO 8601 with offset>"}]}}`; no API key is needed.

## Book

```http
POST https://api.cal.com/v2/bookings
cal-api-version: 2026-02-25
Content-Type: application/json

{
  "eventTypeId": 6292747,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "notes": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address)
- Optional fields: `notes` (Additional notes), `guests` (Add guests)
- `name` and `email` go in `attendee` and `guests` is a list of emails; every other field goes in `bookingFieldsResponses` under its name.
- `location` is optional; without it the booking uses the event’s first location.
