Skip to main content
Glama

open_note

Open a specific note in Bear by providing its unique identifier to access and view content directly.

Instructions

Open a specific note in Bear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYesThe unique identifier of the note (ZUNIQUEIDENTIFIER)

Implementation Reference

  • The actual implementation of the open_note tool, which constructs a bear://x-callback-url and executes it.
    def open_note(note_id: str) -> dict[str, str]:
        """
        Open a specific note in Bear.
    
        Args:
            note_id: The unique identifier of the note (ZUNIQUEIDENTIFIER)
    
        Returns:
            Dictionary with operation result
        """
        params = {"id": note_id}
    
        query_string = urllib.parse.urlencode(params)
        url = f"bear://x-callback-url/open-note?{query_string}"
    
        return _open_bear_url(url)
  • The server-side handler block in the MCP server implementation that maps the 'open_note' tool request to the implementation function.
    elif name == "open_note":
        if not isinstance(arguments, dict) or "note_id" not in arguments:
            raise ValueError("Missing required argument: note_id")
    
        result = open_note(note_id=arguments["note_id"])
        return [TextContent(type="text", text=str(result))]
  • The tool definition and input schema for the 'open_note' tool.
        name="open_note",
        description="Open a specific note in Bear",
        inputSchema={
            "type": "object",
            "properties": {
                "note_id": {
                    "type": "string",
                    "description": "The unique identifier of the note (ZUNIQUEIDENTIFIER)",
                },
            },
            "required": ["note_id"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Open' suggests an interactive or display action, but the description doesn't clarify what 'open' means operationally—whether it launches an app, returns content, or has side effects. 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 is a single, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple tool and front-loaded with essential information.

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 and no output schema, the description is incomplete for a tool that presumably performs an action on a note. It doesn't explain what 'open' entails—whether it returns data, triggers UI, or has other effects—leaving the agent uncertain about outcomes and usage context.

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 the 'note_id' parameter. The description adds no additional semantic context about the parameter beyond what's in the schema, meeting the baseline for high coverage but not providing extra value.

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 ('Open') and target resource ('a specific note in Bear'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_note_by_id' which might retrieve similar information, so it doesn't reach the highest 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 like 'get_note_by_id' or 'get_notes'. It doesn't mention prerequisites, context, or exclusions, leaving the agent to guess 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/maxim-ist/mcp-bear'

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