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"],
    },
Behavior5/5

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

The description adds important behavioral details beyond annotations: it triggers a sync and deletes a local file. This complements the destructiveHint annotation and provides clear expectations.

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 that efficiently convey the core action and a key side effect. No unnecessary information.

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?

The description covers the input, action, and side effect. Without an output schema, the agent might need to infer return behavior, but for a destructive tool this is generally sufficient.

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?

The input schema is simple with one parameter (id) and 100% coverage. The description does not add any additional semantics beyond the schema's own description.

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 action: removing a Bear note from the context library by removing its #context tag. This distinguishes it from siblings like bear_context_add and bear_remove_tag.

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 explicit guidance on when to use this tool versus alternatives. With many sibling tools like bear_remove_tag, the description lacks context for appropriate 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