Skip to main content
Glama

search_bear

Search Bear Notes on macOS to find specific notes using a search term, enabling users to locate and access relevant information stored in their notes database.

Instructions

Open Bear and show search results for a term

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term

Implementation Reference

  • The actual implementation logic for the "search_bear" tool, which constructs a bear:// URL and calls _open_bear_url.
    def search_in_bear(term: str) -> dict[str, str]:
        """
        Open Bear and show search results for a term.
    
        Args:
            term: Search term
    
        Returns:
            Dictionary with operation result
        """
        params = {"term": term}
    
        query_string = urllib.parse.urlencode(params)
        url = f"bear://x-callback-url/search?{query_string}"
    
        return _open_bear_url(url)
  • The tool definition and registration for "search_bear" in the MCP server setup.
    Tool(
        name="search_bear",
        description="Open Bear and show search results for a term",
        inputSchema={
            "type": "object",
            "properties": {
                "term": {
                    "type": "string",
                    "description": "Search term",
                },
            },
            "required": ["term"],
        },
    ),
  • The MCP tool handler dispatch logic that routes "search_bear" calls to the search_in_bear implementation.
    elif name == "search_bear":
        if not isinstance(arguments, dict) or "term" not in arguments:
            raise ValueError("Missing required argument: term")
    
        result = search_in_bear(term=arguments["term"])
        return [TextContent(type="text", text=str(result))]
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 opens Bear and shows search results, but doesn't describe what happens if Bear isn't installed, whether it launches Bear if closed, how results are displayed, if it's interactive, or any side effects. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 extremely concise (one sentence) and front-loaded with the core action. Every word earns its place, with no redundant or vague phrasing. It efficiently communicates the essential purpose without unnecessary detail.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'show search results' entails—whether it returns data, opens a UI, or provides a list. For a tool that interacts with an external application (Bear), more context about behavior and outcomes is needed to be fully helpful to an AI 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?

The schema description coverage is 100%, with the single parameter 'term' clearly documented as 'Search term'. The description adds minimal value beyond the schema by implying the term is used for searching, but doesn't provide additional context like format expectations, examples, or search behavior (e.g., partial matches). Baseline 3 is appropriate given 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 tool's purpose with a specific verb ('Open') and resource ('Bear'), and specifies the action ('show search results for a term'). It distinguishes from siblings like 'open_note' or 'get_notes' by focusing on search functionality. However, it doesn't explicitly differentiate from potential search-related siblings like 'get_notes_like'.

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 when to prefer this over 'get_notes_like' (which might search notes) or 'open_note' (which opens a specific note). There are no prerequisites, exclusions, or contextual recommendations provided.

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/maxim-ist/mcp-bear'

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