ワンクリックで
agentdb-hyperedge
// Search and manage hyperedges — n-ary relationships between memories. Use for swarm membership, multi-cause incidents, or any "this involves all of (A, B, C, D)" relationship that doesn't fit a binary edge.
// Search and manage hyperedges — n-ary relationships between memories. Use for swarm membership, multi-cause incidents, or any "this involves all of (A, B, C, D)" relationship that doesn't fit a binary edge.
Walk the causal graph in AgentDB to explain why two memories are connected, or trace a root cause. Use when the user asks "why did X happen", "what led to Y", or after an incident.
Record a causal relationship between two memories in AgentDB — "X caused Y", "A supersedes B", "patch-foo depends-on patch-bar". Use when the user is documenting cause/effect, dependencies, supersessions, or after-action analysis.
Store memories in tier-aware hierarchical memory — working / short-term / long-term — and recall with tier filters. Use for working-set context that should fade, vs facts that should persist, vs patterns that should be searchable forever.
Initialize an AgentDB Cognitive Container (.rvf file) in the current project. Sets up storage, embedder config, and the agentdb MCP server. Use when the user is starting a new project that needs vector memory, or asks to "set up agentdb" / "init agentdb".
Show AgentDB health — pattern count, embedder status, cache hit rate, learning gain since init. Use when the user asks "is agentdb working?", "how many memories?", "show agentdb stats", or after long-running sessions to confirm state.
Execute Cypher queries against AgentDB's graph backend. Use when the user wants to write a custom traversal that the standard tools don't cover, or when explaining graph state.
| name | agentdb-hyperedge |
| description | Search and manage hyperedges — n-ary relationships between memories. Use for swarm membership, multi-cause incidents, or any "this involves all of (A, B, C, D)" relationship that doesn't fit a binary edge. |
Hyperedges connect more than two nodes — useful when a single relationship genuinely involves many participants.
agentdb_hyperedge_create(
nodes: [<id>, <id>, ...]
description: <one-liner>
embedding?: Float32Array
confidence?: 0..1
metadata?: { ... }
)
agentdb_hyperedge_search(
query: <semantic | nodeId>
topK?: 10
)
agentdb_hyperedge_delete(
id: <hyperedge id>
)
The agentdb_hyperedge_delete tool was added in agentdb 3.0.0-alpha.13.
Hyperedges are searchable by their description embedding — useful for "find all multi-agent collaborations on auth-related work" without enumerating every binary edge.