Skip to main content
Glama

expand

Retrieves the typed-edge neighborhood of seed documents using BFS. Returns citation packets with provenance, filterable by edge type and document properties.

Instructions

Typed-edge BFS retrieval. Returns the typed-edge neighborhood of one or more seed documents as a flat array of citation packets, each carrying via: {seed_doc_id, hop, edge_type, direction} provenance. Hops hard-capped at 2 (v2.0.0). Default direction = 'both'. Filterable by edge_type and by document properties (strict equality, no operators). Memory-sink documents (_memory/...) surface only when they are already linked from a user note in the result set (per ADR-004 memory-namespace opacity rule). Frontmatter-ref edges are extracted heuristically: [[...]] syntax in any property value OR allowlisted property names (assignee, owner, project, related, parent, child, attendees, superseded_by) matched against note_aliases. include_superseded defaults to false (Phase 2 D-03 forward-only supersede). Unknown seed_doc_ids do not throw — they are returned in a warnings: [{seed_doc_id, reason: 'unknown_doc'}] array. Shortest path wins on dedup; ties broken by (seed_doc_id, edge_type, direction).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seed_doc_idsYes1+ opaque DocIds (e.g. obsidian-fs://<vault>/<path>) — seeds of the BFS.
hopsYesHop cap (1 or 2). v2.0.0 hard-caps at 2.
directionNoEdge traversal direction; default 'both'.both
edge_typesNoOptional filter on edge types; default = all four types.
filter_propertiesNoStrict-equality predicate on document properties (e.g. {type: 'Project'}).
include_supersededNoWhen false (default), docs whose properties.status === 'superseded' are dropped.
Behavior5/5

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

With no annotations, the description carries full burden and provides extensive behavioral details: hop cap, default direction, filter capabilities, memory-namespace opacity, frontmatter-ref heuristics, superseded handling, error behavior, and dedup rules. This goes well beyond basic mechanism.

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?

Every sentence provides unique, essential information. The description is dense but not verbose, front-loaded with the main purpose, and efficiently covers all critical aspects without repetition.

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, no output schema), the description is remarkably complete. It explains the return format, provenance metadata, error handling, filtering, and edge cases, enabling an agent to use the tool effectively.

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 coverage is 100% (all 6 parameters described), so baseline is 3. The description adds value by providing context such as version constraints on hops, behavior for unknown seed_doc_ids, and dedup strategy, which are not in the parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a 'Typed-edge BFS retrieval' that returns the typed-edge neighborhood of seed documents. This gives a specific verb and resource, but it does not explicitly distinguish itself from sibling tools like list_forward_links or list_backlinks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (for traversing typed edges with hop limit and filtering), but it does not provide explicit when-to-use or when-not-to-use guidance relative to alternatives. Agents must infer applicability from the feature list.

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/owrede/vault-memory'

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