Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager

bear_search

Search for notes in Bear app using keywords or tags to find specific information quickly.

Instructions

Search for notes in Bear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNoSearch term
tagNoTag to search within
tokenNoBear API token
show_windowNoShow Bear window

Implementation Reference

  • The main handler function for the 'bear_search' tool. It processes input arguments, constructs parameters for Bear's search URL, executes the search via executeWithCallback, and returns the results in a formatted text response.
    private async search(args: any) {
      const params: Record<string, string | boolean> = {};
      
      if (args.term) params.term = args.term;
      if (args.tag) params.tag = args.tag;
      if (args.token) params.token = args.token;
      if (args.show_window) params.show_window = "yes";
    
      const searchData = await this.executeWithCallback("search", params);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              message: `Searched Bear for: ${args.term || "all notes"}${args.tag ? ` in tag: ${args.tag}` : ""}`,
              results: searchData
            }, null, 2)
          }
        ]
      };
    }
  • Defines the tool name, description, and input schema for validation in the ListTools response.
    {
      name: "bear_search",
      description: "Search for notes in Bear",
      inputSchema: {
        type: "object",
        properties: {
          term: {
            type: "string",
            description: "Search term"
          },
          tag: {
            type: "string",
            description: "Tag to search within"
          },
          token: {
            type: "string",
            description: "Bear API token"
          },
          show_window: {
            type: "boolean",
            description: "Show Bear window"
          }
        }
      }
    },
  • src/index.ts:713-714 (registration)
    The switch case that registers and dispatches to the bear_search handler in the CallToolRequestHandler.
    case "bear_search":
      return await this.search(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the action ('search') but doesn't explain what the search returns (e.g., list of notes, note contents, metadata), how results are ordered, whether it's paginated, or any limitations like rate limits or authentication requirements beyond the token parameter. This leaves significant gaps for an agent to understand 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 is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 a search operation with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the search returns, how results are structured, or any behavioral aspects like error handling. For a tool with this level of potential complexity, the description should provide more context to be fully helpful.

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 has 100% description coverage, with all four parameters clearly documented in the schema itself. The tool description adds no additional meaning about parameters beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('search') and resource ('notes in Bear'), making the purpose immediately understandable. However, it doesn't differentiate this search tool from other search-related capabilities that might exist in sibling tools like 'bear_get_today' or 'bear_get_untagged', which could also involve finding notes.

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. With multiple sibling tools that retrieve notes (e.g., 'bear_get_today', 'bear_get_untagged', 'bear_get_locked'), there's no indication of when this general search is preferred over those more specific retrieval methods.

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