Skip to main content
Glama

bear_context_remove

DestructiveIdempotent

Remove a Bear note from the context library by deleting its #context tag, decluttering your curated knowledge base for LLM interactions.

Instructions

Remove a Bear note from the context library by removing its #context tag. Triggers a sync to delete the local file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNote ID (uniqueIdentifier)

Implementation Reference

  • The full handler definition for bear_context_remove. It defines the tool metadata (name, description, input schema requiring an 'id' field), and the buildArgs function which constructs the bcli command: ['context', 'remove', '<id>', '--json']. This removes a Bear note from the context library by removing its #context tag and triggers a sync to delete the local file.
    bear_context_remove: {
      tool: {
        name: "bear_context_remove",
        description:
          "Remove a Bear note from the context library by removing its #context tag. Triggers a sync to delete the local file.",
        inputSchema: {
          type: "object" as const,
          properties: {
            id: {
              type: "string",
              description: "Note ID (uniqueIdentifier)",
            },
          },
          required: ["id"],
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => ["context", "remove", String(input.id), "--json"],
    },
  • The tool is registered automatically by being included in the 'tools' object exported from tools.ts. index.ts iterates over Object.values(tools) to register all tools, including bear_context_remove.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: Object.values(tools).map((t) => t.tool),
    }));
  • The input schema for bear_context_remove requiring a single 'id' parameter (string). No other parameters are accepted.
    bear_context_remove: {
      tool: {
        name: "bear_context_remove",
        description:
          "Remove a Bear note from the context library by removing its #context tag. Triggers a sync to delete the local file.",
        inputSchema: {
          type: "object" as const,
          properties: {
            id: {
              type: "string",
              description: "Note ID (uniqueIdentifier)",
            },
          },
          required: ["id"],
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => ["context", "remove", String(input.id), "--json"],
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.26

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. The description adds specific behavioral context: 'Triggers a sync to delete the local file', which clarifies the consequence of removal. No contradictions with annotations.

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 consists of two short, front-loaded sentences. Every word adds value, with no redundancy or fluff.

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?

For a single-parameter tool with annotations and no output schema, the description covers action, mechanism, and consequence. It is slightly ambiguous whether the note is permanently deleted or just removed from context, but overall it is sufficiently 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 one parameter 'id' described as 'Note ID (uniqueIdentifier)'. The description does not add additional parameter meaning beyond the schema, so baseline score of 3 is appropriate.

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 the verb 'Remove' and the resource 'Bear note from the context library', specifying the mechanism (removing #context tag) and side effect (triggers sync to delete local file). It distinguishes from siblings like bear_context_add and bear_context_remove_external by focusing on internal notes.

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 when wanting to remove a note from the context library, but does not explicitly state when to use this tool versus alternatives like bear_delete_tag or bear_trash_note. No exclusions or alternative suggestions are provided.

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