Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager

bear_get_locked

Retrieve encrypted notes from Bear App using search terms and window display options to access secured content.

Instructions

Get locked (encrypted) notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch term
show_windowNoShow Bear window

Implementation Reference

  • src/index.ts:613-629 (registration)
    Registers the 'bear_get_locked' tool in the ListTools handler, providing name, description, and input schema for parameters like search term and show_window option.
    {
      name: "bear_get_locked",
      description: "Get locked (encrypted) notes",
      inputSchema: {
        type: "object",
        properties: {
          search: {
            type: "string",
            description: "Search term"
          },
          show_window: {
            type: "boolean",
            description: "Show Bear window"
          }
        }
      }
    },
  • src/index.ts:729-730 (registration)
    Switch case in CallToolRequestSchema handler that dispatches 'bear_get_locked' tool calls to the getLocked method.
    case "bear_get_locked":
      return await this.getLocked(args);
  • Core handler function for 'bear_get_locked' tool. Builds a Bear x-callback-url for the 'locked' action with optional search and show_window parameters, executes it, and returns a success message.
    private async getLocked(args: any) {
      const params: Record<string, string | boolean> = {};
      
      if (args.search) params.search = args.search;
      if (args.show_window) params.show_window = "yes";
    
      const url = this.buildBearURL("locked", params);
      await this.executeURL(url);
    
      return {
        content: [
          {
            type: "text",
            text: `Retrieved locked notes${args.search ? ` matching: ${args.search}` : ""}`
          }
        ]
      };
    }
  • Input schema defining parameters for the bear_get_locked tool: optional search string and show_window boolean.
    inputSchema: {
      type: "object",
      properties: {
        search: {
          type: "string",
          description: "Search term"
        },
        show_window: {
          type: "boolean",
          description: "Show Bear window"
        }
      }
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. It states the tool retrieves locked notes but lacks details on permissions required, whether it lists or opens notes, response format, or error handling. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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, efficient sentence with zero waste. It front-loads the core purpose ('Get locked notes') and avoids unnecessary elaboration, making it easy to parse quickly. Every word earns its place by directly contributing to understanding the tool's function.

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 the complexity of retrieving encrypted notes, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'locked' entails (e.g., encryption status), how results are returned, or any limitations. For a tool that likely involves security considerations, this leaves too much unspecified for reliable agent use.

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 the two parameters (search and show_window). The description adds no additional meaning beyond implying a retrieval action, which the schema already supports. This meets the baseline score of 3, as the schema handles parameter documentation adequately.

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 verb 'Get' and the resource 'locked (encrypted) notes', making the purpose immediately understandable. It distinguishes this tool from siblings like bear_search or bear_get_today by specifying it retrieves only encrypted notes. However, it doesn't explicitly contrast with all siblings (e.g., bear_get_untagged), keeping it from a perfect score.

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. It doesn't mention prerequisites (e.g., needing encrypted notes), exclusions, or comparisons to siblings like bear_search (which might also find locked notes). Without such context, an agent must infer usage from the name 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