Skip to main content
Glama

bear_context_add

Idempotent

Tag a Bear note with #context to add it to your context library. Optionally specify a subtag like #context/jira for grouping.

Instructions

Add a Bear note to the context library by tagging it with #context. Optionally specify a subtag for grouping (e.g., subtag 'jira' → #context/jira). Triggers a sync after tagging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNote ID (uniqueIdentifier)
subtagNoOptional sub-tag for grouping (e.g., 'architecture', 'jira')

Implementation Reference

  • Schema definition: input validation and tool metadata for bear_context_add. Requires 'id' (string), optional 'subtag' (string). It's non-destructive and idempotent.
    tool: {
      name: "bear_context_add",
      description:
        "Add a Bear note to the context library by tagging it with #context. Optionally specify a subtag for grouping (e.g., subtag 'jira' → #context/jira). Triggers a sync after tagging.",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: {
            type: "string",
            description: "Note ID (uniqueIdentifier)",
          },
          subtag: {
            type: "string",
            description:
              "Optional sub-tag for grouping (e.g., 'architecture', 'jira')",
          },
        },
        required: ["id"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: true,
      },
  • Handler/buildArgs: builds CLI args to invoke external bcli tool with 'context add <id> --json' and optionally '--subtag <subtag>'. This is the core execution logic - the tool delegates to the bcli binary.
    buildArgs: (input) => {
      const args = ["context", "add", String(input.id), "--json"];
      if (input.subtag) args.push("--subtag", String(input.subtag));
      return args;
    },
  • Registration: the tool is defined as an entry in the exported 'tools' Record<string, ToolHandler> map at line 9. It is discoverable by the MCP server via Object.values(tools) in index.ts.
    bear_context_add: {
      tool: {
        name: "bear_context_add",
        description:
          "Add a Bear note to the context library by tagging it with #context. Optionally specify a subtag for grouping (e.g., subtag 'jira' → #context/jira). Triggers a sync after tagging.",
        inputSchema: {
          type: "object" as const,
          properties: {
            id: {
              type: "string",
              description: "Note ID (uniqueIdentifier)",
            },
            subtag: {
              type: "string",
              description:
                "Optional sub-tag for grouping (e.g., 'architecture', 'jira')",
            },
          },
          required: ["id"],
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => {
        const args = ["context", "add", String(input.id), "--json"];
        if (input.subtag) args.push("--subtag", String(input.subtag));
        return args;
      },
    },
Behavior4/5

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

Annotations already mark as mutable and idempotent; description adds that tagging triggers a sync, providing useful behavioral context beyond 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?

Two concise sentences with no fluff. Front-loaded with core action and optional details.

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, and description omits return value or error handling info. Agents may need to know sync success reporting.

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 has 100% coverage; description adds meaning by explaining subtag becomes #context/subtag and sync behavior, complementing the schema well.

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?

Clearly states the action: adding a Bear note to the context library by tagging with #context. Distinguishes from siblings like bear_context_remove.

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?

Describes optional subtag for grouping and mentions sync triggering, but does not specify when to use vs. 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/KuvopLLC/better-bear'

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