Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager

bear_archive_note

Archive notes in Bear App by ID or search term to organize your workspace and reduce clutter.

Instructions

Archive a note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNote unique identifier
searchNoSearch term to find notes to archive
show_windowNoShow Bear window

Implementation Reference

  • The main handler function for the 'bear_archive_note' tool. It constructs parameters from input args, builds a Bear x-callback URL with action 'archive', executes it using the system's 'open' command, and returns a success message.
    private async archiveNote(args: any) {
      const params: Record<string, string | boolean> = {};
      
      if (args.id) params.id = args.id;
      if (args.search) params.search = args.search;
      if (args.show_window) params.show_window = "yes";
    
      const url = this.buildBearURL("archive", params);
      await this.executeURL(url);
    
      return {
        content: [
          {
            type: "text",
            text: `Archived note(s)${args.id ? ` with ID: ${args.id}` : args.search ? ` matching: ${args.search}` : ""}`
          }
        ]
      };
    }
  • The input schema defining the parameters for the 'bear_archive_note' tool: id (string), search (string), show_window (boolean).
      type: "object",
      properties: {
        id: {
          type: "string",
          description: "Note unique identifier"
        },
        search: {
          type: "string",
          description: "Search term to find notes to archive"
        },
        show_window: {
          type: "boolean",
          description: "Show Bear window"
        }
      }
    }
  • src/index.ts:529-549 (registration)
    The tool registration in the list of available tools returned by ListToolsRequestSchema, including name, description, and inputSchema.
    {
      name: "bear_archive_note",
      description: "Archive a note",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "Note unique identifier"
          },
          search: {
            type: "string",
            description: "Search term to find notes to archive"
          },
          show_window: {
            type: "boolean",
            description: "Show Bear window"
          }
        }
      }
    },
  • src/index.ts:721-722 (registration)
    The dispatch case in the CallToolRequestSchema handler's switch statement that routes calls to the archiveNote handler method.
    case "bear_archive_note":
      return await this.archiveNote(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Archive a note' implies a mutation operation, but it doesn't specify permissions needed, whether archiving is reversible, what happens to archived notes, or any rate limits. This leaves significant gaps in understanding the tool's behavior.

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 'Archive a note' is extremely concise with zero wasted words, front-loading the core action. It's appropriately sized for a simple tool, though this brevity contributes to gaps in other dimensions.

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

Completeness2/5

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

Given no annotations, no output schema, and a mutation tool with 3 parameters, the description is incomplete. It fails to explain the tool's effects, return values, or how to handle parameters like 'id' versus 'search', making it inadequate for safe and effective use by an agent.

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 description coverage is 100%, so the input schema fully documents parameters like 'id', 'search', and 'show_window'. The description adds no additional meaning beyond this, such as explaining how 'id' and 'search' interact or what 'show_window' affects. Baseline 3 is appropriate as the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Archive a note' clearly states the action (archive) and resource (note), providing basic purpose. However, it doesn't differentiate from sibling tools like 'bear_trash_note' or explain what archiving means in this context versus trashing or deleting, making it vague about the specific operation.

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 is provided on when to use this tool versus alternatives such as 'bear_trash_note' or 'bear_delete_tag', nor are there any prerequisites or context for archiving. The description lacks any usage instructions, leaving the agent to infer based on tool names alone.

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/bigjeager/bear-mcp-server'

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