Skip to main content
Glama

bear_delete_tag

DestructiveIdempotent

Remove a specified tag from all Bear notes while preserving the notes themselves.

Instructions

Delete a tag from all Bear notes. The tag text is removed but notes are preserved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYesTag to delete (without #)

Implementation Reference

  • Tool definition and registration for bear_delete_tag. Defines the tool name, description, input schema (required 'tag' string), annotations (destructive, idempotent), and buildArgs function that constructs the CLI command: ['tag', 'delete', String(input.tag), '--json'].
    bear_delete_tag: {
      tool: {
        name: "bear_delete_tag",
        description:
          "Delete a tag from all Bear notes. The tag text is removed but notes are preserved.",
        inputSchema: {
          type: "object" as const,
          properties: {
            tag: {
              type: "string",
              description: "Tag to delete (without #)",
            },
          },
          required: ["tag"],
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => [
        "tag",
        "delete",
        String(input.tag),
        "--json",
      ],
    },
  • Input schema for bear_delete_tag. Requires one parameter: 'tag' (string) - the tag to delete (without #).
    inputSchema: {
      type: "object" as const,
      properties: {
        tag: {
          type: "string",
          description: "Tag to delete (without #)",
        },
      },
      required: ["tag"],
    },
  • Generic tool request handler that routes all tool calls (including bear_delete_tag) via the tools registry. Calls handler.buildArgs(params) to get CLI args, then executes them via execBcliWithReauth (or execBcliWithStdinAndReauth if usesStdin is defined). Results are parsed as JSON and returned.
    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,
        };
      }
    });

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.26

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent. Description adds value by clarifying notes are preserved, which resolves potential ambiguity. No contradiction.

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 concise sentences with no redundant information. Perfect front-loading of action and effect.

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?

For a simple delete operation, all necessary information is present: purpose, effect, parameter format. Output schema not needed. Annotations and siblings provide context.

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 provides 100% description coverage including the 'without #' convention. Description adds no additional meaning beyond schema.

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?

Clearly states the verb 'Delete' and resource 'tag' with scope 'from all Bear notes'. Implicitly distinguishes from sibling bear_remove_tag by global scope, but does not explicitly compare.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like bear_remove_tag or bear_rename_tag. The description only states functionality without usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.