Skip to main content
Glama

bear_context_push_to_bear

Idempotent

Moves a matured external file into Bear as a new note, adding #context tags and deleting the original.

Instructions

Push an external file to Bear as a new note. Creates a Bear note from the file content, tags it with #context (+ optional subtag), and removes the original external file. Use when external content has matured enough to become a permanent Bear note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesFilename in external/ to push
subtagNoSub-tag (e.g., 'architecture' → #context/architecture)
titleNoOverride note title (defaults to title extracted from content)

Implementation Reference

  • Registration of all tools including bear_context_push_to_bear in the tools map
    export const tools: Record<string, ToolHandler> = {
  • Complete handler definition for bear_context_push_to_bear: tool definition with schema, annotations, and buildArgs function that constructs 'context push' CLI command
    bear_context_push_to_bear: {
      tool: {
        name: "bear_context_push_to_bear",
        description:
          "Push an external file to Bear as a new note. Creates a Bear note from the file content, tags it with #context (+ optional subtag), and removes the original external file. Use when external content has matured enough to become a permanent Bear note.",
        inputSchema: {
          type: "object" as const,
          properties: {
            filename: {
              type: "string",
              description: "Filename in external/ to push",
            },
            subtag: {
              type: "string",
              description:
                "Sub-tag (e.g., 'architecture' → #context/architecture)",
            },
            title: {
              type: "string",
              description:
                "Override note title (defaults to title extracted from content)",
            },
          },
          required: ["filename"],
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => {
        const args = ["context", "push", String(input.filename), "--json"];
        if (input.subtag) args.push("--subtag", String(input.subtag));
        if (input.title) args.push("--title", String(input.title));
        return args;
      },
    },
  • Input schema for bear_context_push_to_bear: filename (required), subtag (optional), title (optional)
    inputSchema: {
      type: "object" as const,
      properties: {
        filename: {
          type: "string",
          description: "Filename in external/ to push",
        },
        subtag: {
          type: "string",
          description:
            "Sub-tag (e.g., 'architecture' → #context/architecture)",
        },
        title: {
          type: "string",
          description:
            "Override note title (defaults to title extracted from content)",
        },
      },
      required: ["filename"],
    },
  • Server handler that dispatches tool calls: looks up tool by name, calls buildArgs, and executes via bcli
    import { tools } from "./tools.js";
    
    function createServer(): Server {
      const server = new Server(
        {
          name: "better-bear",
          version: "0.4.0",
        },
        {
          capabilities: {
            tools: {},
          },
        },
      );
    
      server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: Object.values(tools).map((t) => t.tool),
      }));
    
      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,
          };
        }
      });
    
      return server;
Behavior1/5

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

Description says it 'removes the original external file,' which is a destructive action, but annotations set destructiveHint=false. This contradiction makes the description misleading.

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 sentences, front-loaded with action and resource, no redundant words. Every sentence earns its place.

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

Completeness3/5

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

No output schema, but description does not mention return value or error cases. Lacks completeness for a mutation tool, though core behavior is covered.

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 parameters described in schema). Description adds value by explaining filename path ('external/'), subtag format ('#context/subtag'), and title override, going beyond schema details.

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 uses a specific verb ('Push') and resource ('external file to Bear as a new note'), clearly distinguishing it from sibling tools like bear_context_add or bear_create_note. It states the action and context.

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?

Explicitly states when to use: 'when external content has matured enough to become a permanent Bear note.' This provides clear guidance, though it does not list alternatives or when not to use.

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