Skip to main content
Glama

bear_context_setup

Idempotent

Initialize a context library for Bear notes, creating a synced folder curated for LLM consumption. Sets up directory structure and configuration for tag-based note inclusion.

Instructions

Initialize a context library — a curated, synced folder of Bear notes optimized for LLM consumption. Creates the directory structure and config. After setup, tag Bear notes with #context (or a custom prefix) and use bear_context_sync to pull them in. One-time operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dirNoOutput directory for the context library (default: ~/.bear-context)
tag_prefixNoTag prefix for qualifying notes (default: context). Notes tagged #context or #context/subtag will be included.
use_frontmatterNoAlso include notes with context: true in YAML front matter (default: true)

Implementation Reference

  • The full tool definition for bear_context_setup, including the 'tool' object (name, description, inputSchema, annotations) and the 'buildArgs' function that constructs the CLI command ['context', 'init', '--json'] along with optional flags (--dir, --tag-prefix, --frontmatter). This is the primary handler that executes the tool logic by building the arguments passed to the bcli executable.
    bear_context_setup: {
      tool: {
        name: "bear_context_setup",
        description:
          "Initialize a context library — a curated, synced folder of Bear notes optimized for LLM consumption. Creates the directory structure and config. After setup, tag Bear notes with #context (or a custom prefix) and use bear_context_sync to pull them in. One-time operation.",
        inputSchema: {
          type: "object" as const,
          properties: {
            dir: {
              type: "string",
              description:
                "Output directory for the context library (default: ~/.bear-context)",
            },
            tag_prefix: {
              type: "string",
              description:
                "Tag prefix for qualifying notes (default: context). Notes tagged #context or #context/subtag will be included.",
            },
            use_frontmatter: {
              type: "boolean",
              description:
                "Also include notes with context: true in YAML front matter (default: true)",
            },
          },
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => {
        const args = ["context", "init", "--json"];
        if (input.dir) args.push("--dir", String(input.dir));
        if (input.tag_prefix)
          args.push("--tag-prefix", String(input.tag_prefix));
        if (input.use_frontmatter === true) args.push("--frontmatter");
        return args;
      },
    },
  • Input schema for bear_context_setup defining the three optional parameters: dir (string), tag_prefix (string), and use_frontmatter (boolean).
    inputSchema: {
      type: "object" as const,
      properties: {
        dir: {
          type: "string",
          description:
            "Output directory for the context library (default: ~/.bear-context)",
        },
        tag_prefix: {
          type: "string",
          description:
            "Tag prefix for qualifying notes (default: context). Notes tagged #context or #context/subtag will be included.",
        },
        use_frontmatter: {
          type: "boolean",
          description:
            "Also include notes with context: true in YAML front matter (default: true)",
        },
      },
    },
  • The CallToolRequestSchema handler in index.ts that looks up tools by name (line 35: const handler = tools[name]) and dispatches execution. This is where bear_context_setup is registered and invoked at runtime.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: input } = request.params;
      const handler = tools[name];
    
      if (!handler) {
        return {
          content: [{ type: "text", text: `Unknown tool: ${name}` }],
          isError: true,
        };
      }
    
      const params = (input ?? {}) as Record<string, unknown>;
    
      // Validate bear_edit_note: need at least one edit operation
      if (name === "bear_edit_note") {
        const hasAppend = params.append_text !== undefined;
        const hasBody = params.body !== undefined;
        const hasSetFm = params.set_frontmatter !== undefined &&
          Object.keys(params.set_frontmatter as object).length > 0;
        const hasRemoveFm = Array.isArray(params.remove_frontmatter) &&
          (params.remove_frontmatter as unknown[]).length > 0;
        const hasFm = hasSetFm || hasRemoveFm;
    
        if (!hasAppend && !hasBody && !hasFm) {
          return {
            content: [
              {
                type: "text",
                text: "Provide 'append_text', 'body', 'set_frontmatter', or 'remove_frontmatter'.",
              },
            ],
            isError: true,
          };
        }
        if (hasAppend && hasBody) {
          return {
            content: [
              {
                type: "text",
                text: "Provide either 'append_text' or 'body', not both.",
              },
            ],
            isError: true,
          };
        }
      }
    
      try {
        const args = handler.buildArgs(params);
        let result: { stdout: string; stderr: string };
    
        // Check if this tool needs stdin piping
        const stdinData = handler.usesStdin?.(params) ?? null;
        if (stdinData !== null) {
          result = await execBcliWithStdinAndReauth(args, stdinData);
        } else {
          result = await execBcliWithReauth(args);
        }
    
        // Parse JSON output from bcli
        const stdout = result.stdout.trim();
        if (!stdout) {
          return {
            content: [{ type: "text", text: "Command completed successfully." }],
          };
        }
    
        // Validate it's JSON and pretty-print
        try {
          const parsed = JSON.parse(stdout);
          return {
            content: [
              { type: "text", text: JSON.stringify(parsed, null, 2) },
            ],
          };
        } catch {
          // If bcli returned non-JSON, pass it through
          return {
            content: [{ type: "text", text: stdout }],
          };
        }
      } catch (error) {
        const message =
          error instanceof BcliError ? error.message : String(error);
        return {
          content: [{ type: "text", text: message }],
          isError: true,
        };
      }
    });
  • The ListToolsRequestSchema handler that registers all tools (including bear_context_setup) by exposing them via Object.values(tools).map(t => t.tool).
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: Object.values(tools).map((t) => t.tool),
    }));
Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds that it creates directory structure and config, but says 'one-time operation,' which could conflict with idempotency. It does not detail behavior if the directory already exists.

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 three concise sentences, front-loaded with the primary purpose, then usage instructions. Every sentence is informative with no unnecessary words.

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?

Given the tool has optional parameters and no output schema, the description explains the concept and workflow. It could be more explicit about idempotent behavior (already in annotations) and what happens on re-run, but overall it is fairly complete.

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 100% with clear descriptions for each parameter. The description mentions defaults (dir, tag_prefix) but does not add significant meaning beyond what the schema already provides.

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?

The description clearly states it initializes a context library, creates directory structure and config. It distinguishes from siblings by describing it as a one-time setup, while siblings like bear_context_sync are for ongoing synchronization.

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

Usage Guidelines4/5

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

The description provides clear usage context: run this first, then tag notes and use bear_context_sync. It implies this is for initial setup, not for regular use. However, it does not explicitly exclude scenarios where re-running is necessary or appropriate.

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/mreider/better-bear'

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