Hebbrix MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

hebbrix_graph_query

Read-onlyIdempotent

Explore an entity's relationships and facts by traversing outward through the knowledge graph. Use optional timestamps to retrieve historical states and adjust depth for broader or narrower results.

Instructions

Traverse the knowledge graph OUT FROM a named entity to find its relationships and facts. Pass an ISO timestamp to ask what was true at that point in time (bi-temporal). depth = graph hops (1-5).

For a free-text question ("who works at Sequoia?"), use hebbrix_ask (it does search + graph + profile and synthesizes an answer) — this endpoint traverses from a known entity, not from prose.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity": "<entity>"
    },
    "name": "hebbrix_graph_query"
  }
}

Input Schema

Name	Required	Description	Default
`depth`	No
`entity`	Yes
`timestamp`	No
`collection_id`	No
`relation_type`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.3.20Aug 2, 2026

removedInput schema / properties / entity / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / entity / default
```
Removed value: -null
```
addedInput schema / properties / entity / type
```
Added value: +"string"
```

removedInput schema / properties / query

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Query"
-}

addedInput schema / required
```
Added value: +[
+  "entity"
+]
```

First observedv0.3.3Jul 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate a read-only, idempotent, non-destructive operation. The description adds useful behavior context beyond annotations by explaining bi-temporal timestamp semantics and depth range (1-5), which are not inferable from the schema alone.

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?

Two concise paragraphs: the first introduces the core function and key parameters; the second provides a clear use-case differentiation. No word is wasted, making it easy to scan and understand quickly.

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?

For a graph traversal tool with an output schema present, the description covers the essential usage: what it does, how to use the primary parameters, and when to choose an alternative. Minor omissions like relation_type and collection_id filtering options prevent a perfect score, but these are intuitive from their names.

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 coverage is 0%, so the description must illuminate parameters. It effectively explains 'timestamp' (ISO format, bi-temporal) and 'depth' (graph hops, 1-5), but omits 'relation_type' and 'collection_id' which are left entirely to the schema. This partially compensates for the missing parameter documentation.

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?

Clearly states the tool traverses a knowledge graph from a named entity to find relationships and facts, with a specific verb-resource pairing. It explicitly distinguishes itself from hebbrix_ask by contrasting entity-based traversal vs free-text querying.

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?

Provides explicit when-to-use guidance by directing free-text questions to hebbrix_ask while clarifying this tool is for known entities. This direct comparison with a specific sibling alternative makes the usage context unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.