Skip to main content
Glama
camiloluvino

Roam Research MCP Server

by camiloluvino

roam_search_hierarchy

Navigate Roam Research block hierarchies by searching for parent or child blocks from a given starting point, enabling structured exploration of connected knowledge.

Instructions

Search for parent or child blocks in the block hierarchy. Can search up or down the hierarchy from a given block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_uidNoOptional: UID of the block to find children of
child_uidNoOptional: UID of the block to find parents of
page_title_uidNoOptional: Title or UID of the page to search in (UID is preferred for accuracy).
max_depthNoOptional: How many levels deep to search (default: 1)

Implementation Reference

  • Core implementation of the roam_search_hierarchy tool. Executes Datomic queries to retrieve either descendants (children hierarchy) of a parent_uid or ancestors (parent hierarchy) of a child_uid, optionally limited to a specific page. Resolves block references in content and includes depth information.
    export class HierarchySearchHandler extends BaseSearchHandler {
      constructor(
        graph: Graph,
        private params: HierarchySearchParams
      ) {
        super(graph);
      }
    
      async execute(): Promise<SearchResult> {
        const { parent_uid, child_uid, page_title_uid, max_depth = 1 } = this.params;
    
        if (!parent_uid && !child_uid) {
          return {
            success: false,
            matches: [],
            message: 'Either parent_uid or child_uid must be provided'
          };
        }
    
        // Get target page UID if provided
        let targetPageUid: string | undefined;
        if (page_title_uid) {
          targetPageUid = await SearchUtils.findPageByTitleOrUid(this.graph, page_title_uid);
        }
    
        // Define ancestor rule for recursive traversal
        const ancestorRule = `[
          [ (ancestor ?child ?parent) 
              [?parent :block/children ?child] ]
          [ (ancestor ?child ?a) 
              [?parent :block/children ?child] 
              (ancestor ?parent ?a) ]
        ]`;
    
        let queryStr: string;
        let queryParams: any[];
    
        if (parent_uid) {
          // Search for all descendants using ancestor rule
          if (targetPageUid) {
            queryStr = `[:find ?block-uid ?block-str ?depth
                        :in $ % ?parent-uid ?page-uid
                        :where [?p :block/uid ?page-uid]
                               [?parent :block/uid ?parent-uid]
                               (ancestor ?b ?parent)
                               [?b :block/string ?block-str]
                               [?b :block/uid ?block-uid]
                               [?b :block/page ?p]
                               [(get-else $ ?b :block/path-length 1) ?depth]]`;
            queryParams = [ancestorRule, parent_uid, targetPageUid];
          } else {
            queryStr = `[:find ?block-uid ?block-str ?page-title ?depth
                        :in $ % ?parent-uid
                        :where [?parent :block/uid ?parent-uid]
                               (ancestor ?b ?parent)
                               [?b :block/string ?block-str]
                               [?b :block/uid ?block-uid]
                               [?b :block/page ?p]
                               [?p :node/title ?page-title]
                               [(get-else $ ?b :block/path-length 1) ?depth]]`;
            queryParams = [ancestorRule, parent_uid];
          }
        } else {
          // Search for ancestors using the same rule
          if (targetPageUid) {
            queryStr = `[:find ?block-uid ?block-str ?depth
                        :in $ % ?child-uid ?page-uid
                        :where [?p :block/uid ?page-uid]
                               [?child :block/uid ?child-uid]
                               (ancestor ?child ?b)
                               [?b :block/string ?block-str]
                               [?b :block/uid ?block-uid]
                               [?b :block/page ?p]
                               [(get-else $ ?b :block/path-length 1) ?depth]]`;
            queryParams = [ancestorRule, child_uid, targetPageUid];
          } else {
            queryStr = `[:find ?block-uid ?block-str ?page-title ?depth
                        :in $ % ?child-uid
                        :where [?child :block/uid ?child-uid]
                               (ancestor ?child ?b)
                               [?b :block/string ?block-str]
                               [?b :block/uid ?block-uid]
                               [?b :block/page ?p]
                               [?p :node/title ?page-title]
                               [(get-else $ ?b :block/path-length 1) ?depth]]`;
            queryParams = [ancestorRule, child_uid];
          }
        }
    
        const rawResults = await q(this.graph, queryStr, queryParams) as [string, string, string?, number?][];
        
        // Resolve block references and format results to include depth information
        const matches = await Promise.all(rawResults.map(async ([uid, content, pageTitle, depth]) => {
          const resolvedContent = await resolveRefs(this.graph, content);
          return {
            block_uid: uid,
            content: resolvedContent,
            depth: depth || 1,
            ...(pageTitle && { page_title: pageTitle })
          };
        }));
    
        const searchDescription = parent_uid
          ? `descendants of block ${parent_uid}`
          : `ancestors of block ${child_uid}`;
    
        return {
          success: true,
          matches,
          message: `Found ${matches.length} block(s) as ${searchDescription}`
        };
      }
    }
  • Input schema definition for the roam_search_hierarchy tool, including parameters for searching hierarchy up or down from a block.
    [toolName(BASE_TOOL_NAMES.SEARCH_HIERARCHY)]: {
      name: toolName(BASE_TOOL_NAMES.SEARCH_HIERARCHY),
      description: 'Search for parent or child blocks in the block hierarchy. Can search up or down the hierarchy from a given block.',
      inputSchema: {
        type: 'object',
        properties: {
          parent_uid: {
            type: 'string',
            description: 'Optional: UID of the block to find children of'
          },
          child_uid: {
            type: 'string',
            description: 'Optional: UID of the block to find parents of'
          },
          page_title_uid: {
            type: 'string',
            description: 'Optional: Title or UID of the page to search in (UID is preferred for accuracy).'
          },
          max_depth: {
            type: 'integer',
            description: 'Optional: How many levels deep to search (default: 1)',
            minimum: 1,
            maximum: 10
          }
        }
        // Note: Validation for either parent_uid or child_uid is handled in the server code
      }
    },
  • MCP tool registration and dispatching for roam_search_hierarchy in the server request handler, including input validation.
    case BASE_TOOL_NAMES.SEARCH_HIERARCHY: {
      const params = request.params.arguments as {
        parent_uid?: string;
        child_uid?: string;
        page_title_uid?: string;
        max_depth?: number;
      };
    
      // Validate that either parent_uid or child_uid is provided, but not both
      if ((!params.parent_uid && !params.child_uid) || (params.parent_uid && params.child_uid)) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          'Either parent_uid or child_uid must be provided, but not both'
        );
      }
    
      const result = await this.toolHandlers.searchHierarchy(params);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
  • Tool handler wrapper method that delegates to SearchOperations.searchHierarchy
    async searchHierarchy(params: {
      parent_uid?: string;
      child_uid?: string;
      page_title_uid?: string;
      max_depth?: number;
    }) {
      return this.searchOps.searchHierarchy(params);
    }
  • Constant definition for the base tool name 'roam_search_hierarchy' used in schema and registration.
    SEARCH_HIERARCHY: 'roam_search_hierarchy',
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the ability to search 'up or down' and 'from a given block,' but doesn't cover critical aspects like whether this is a read-only operation, potential performance impacts, rate limits, authentication needs, or what the output looks like (since there's no output schema). For a search tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is highly concise and front-loaded: two sentences that directly state the tool's purpose and key capability ('search up or down'). There's no wasted verbiage, and every sentence earns its place by conveying essential information efficiently, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (hierarchical search with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the return values, error conditions, or behavioral nuances like how parameters interact (e.g., if both parent_uid and child_uid are provided). For a search tool without structured output or safety hints, more context is needed to ensure reliable agent usage.

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 description coverage is 100%, meaning all parameters are documented in the schema itself (e.g., parent_uid for finding children, child_uid for finding parents, page_title_uid for scoping, max_depth for depth control). The description adds no additional parameter semantics beyond what the schema provides, such as clarifying interactions between parameters or usage examples. With high schema coverage, the baseline is 3, as the description doesn't compensate with extra insights.

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 the tool's purpose: 'Search for parent or child blocks in the block hierarchy. Can search up or down the hierarchy from a given block.' This specifies the verb ('search'), resource ('parent or child blocks'), and scope ('block hierarchy'), distinguishing it from siblings like roam_search_by_text or roam_search_block_refs. However, it doesn't explicitly differentiate from all siblings (e.g., roam_fetch_block_with_children), keeping it at 4 rather than 5.

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 by stating 'Can search up or down the hierarchy from a given block,' which suggests when to use it (for hierarchical searches) but doesn't provide explicit guidance on when to choose this tool over alternatives like roam_search_block_refs or roam_fetch_block_with_children. No exclusions or prerequisites are mentioned, so it's adequate but lacks detailed differentiation.

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/camiloluvino/roamMCP'

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