Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager

bear_trash_note

Move notes to trash in Bear App by specifying a note ID or search term to find and remove unwanted content.

Instructions

Move a note to trash

Input Schema

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

Implementation Reference

  • The main handler function for the 'bear_trash_note' tool. It builds a Bear x-callback URL with action 'trash' using the provided note ID or search term, executes it, and returns a success message.
    private async trashNote(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("trash", params);
      await this.executeURL(url);
    
      return {
        content: [
          {
            type: "text",
            text: `Moved note(s) to trash${args.id ? ` with ID: ${args.id}` : args.search ? ` matching: ${args.search}` : ""}`
          }
        ]
      };
    }
  • Input schema for the bear_trash_note tool, defining optional parameters: id (string), search (string), show_window (boolean).
    inputSchema: {
      type: "object",
      properties: {
        id: {
          type: "string",
          description: "Note unique identifier"
        },
        search: {
          type: "string",
          description: "Search term to find notes to trash"
        },
        show_window: {
          type: "boolean",
          description: "Show Bear window"
        }
      }
    }
  • src/index.ts:508-528 (registration)
    Tool registration in the listTools response, including name, description, and input schema.
    {
      name: "bear_trash_note",
      description: "Move a note to trash",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "Note unique identifier"
          },
          search: {
            type: "string",
            description: "Search term to find notes to trash"
          },
          show_window: {
            type: "boolean",
            description: "Show Bear window"
          }
        }
      }
    },
  • src/index.ts:719-720 (registration)
    Dispatch registration in the CallToolRequest handler switch statement, mapping the tool name to the trashNote method.
    case "bear_trash_note":
      return await this.trashNote(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Move a note to trash' implies a destructive mutation, but it doesn't clarify if this is reversible, what permissions are required, whether it affects linked data, or what the response looks like. For a mutation tool with zero annotation coverage, this lacks critical behavioral context.

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 is a single, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration. This is an excellent example of conciseness for a simple tool.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like reversibility, error conditions, or response format, which are crucial for safe agent operation. The high schema coverage helps with parameters, but overall context is lacking for a destructive operation.

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 schema fully documents all three parameters (id, search, show_window). The description adds no additional parameter semantics beyond what's in the schema, such as explaining how 'id' and 'search' interact or the implications of 'show_window'. Baseline 3 is appropriate when the schema handles parameter documentation.

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?

The description clearly states the action ('Move') and resource ('a note to trash'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'bear_delete_tag' or 'bear_archive_note' by specifying the trash destination rather than deletion or archiving. However, it doesn't explicitly contrast with 'bear_archive_note' which might be a close alternative.

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?

The description provides no guidance on when to use this tool versus alternatives like 'bear_archive_note' or 'bear_delete_tag', nor does it mention prerequisites or constraints. It simply states what the tool does without contextual usage information, leaving the agent to infer when this operation is appropriate.

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