Skip to main content
Glama

create_note

Create notes in Bear with titles, Markdown content, tags, and options to pin or open immediately.

Instructions

Create a new note in Bear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNote title
textNoNote content (supports Markdown)
tagsNoList of tags to add (without # prefix)
pinNoPin the note to the top
open_noteNoOpen the note in Bear after creation

Implementation Reference

  • The core logic that implements the create_note functionality by constructing a bear:// URL and invoking it via macOS 'open'.
    def create_note(
        title: Optional[str] = None,
        text: Optional[str] = None,
        tags: Optional[list[str]] = None,
        pin: bool = False,
        open_note: bool = False
    ) -> dict[str, str]:
        """
        Create a new note in Bear.
    
        Args:
            title: Note title
            text: Note content (supports Markdown)
            tags: List of tags to add (without # prefix)
            pin: Pin the note to the top of the list
            open_note: Open the note in Bear after creation
    
        Returns:
            Dictionary with operation result
        """
        params = {}
    
        if title:
            params["title"] = title
        if text:
            params["text"] = text
        if tags:
            # Join tags with commas
            params["tags"] = ",".join(tags)
        if pin:
            params["pin"] = "yes"
        if open_note:
            params["open_note"] = "yes"
    
        query_string = urllib.parse.urlencode(params)
        url = f"bear://x-callback-url/create?{query_string}"
    
        return _open_bear_url(url)
  • The MCP tool registration for 'create_note', defining its input schema.
        name="create_note",
        description="Create a new note in Bear",
        inputSchema={
            "type": "object",
            "properties": {
                "title": {
                    "type": "string",
                    "description": "Note title",
                },
                "text": {
                    "type": "string",
                    "description": "Note content (supports Markdown)",
                },
                "tags": {
                    "type": "array",
                    "items": {"type": "string"},
                    "description": "List of tags to add (without # prefix)",
                },
                "pin": {
                    "type": "boolean",
                    "description": "Pin the note to the top",
                    "default": False,
                },
                "open_note": {
                    "type": "boolean",
                    "description": "Open the note in Bear after creation",
                    "default": False,
                },
            },
        },
    ),
  • The handler logic within the MCP server that parses the tool arguments and calls the backend create_note function.
    elif name == "create_note":
        if not isinstance(arguments, dict):
            raise ValueError("Invalid arguments")
    
        result = create_note(
            title=arguments.get("title"),
            text=arguments.get("text"),
            tags=arguments.get("tags"),
            pin=arguments.get("pin", False),
            open_note=arguments.get("open_note", False)
        )
        return [TextContent(type="text", text=str(result))]
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states the tool creates a note but doesn't cover permissions needed, whether creation is idempotent, error conditions (e.g., duplicate titles), or what happens on success (e.g., returns a note ID). This leaves significant gaps for a mutation tool.

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, direct sentence with zero wasted words. It front-loads the core purpose ('Create a new note in Bear') without unnecessary elaboration, making it highly efficient and easy to parse.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., whether the note is saved locally, synced, or returns an identifier), error handling, or dependencies like Bear being installed. This leaves critical context gaps for an 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?

Schema description coverage is 100%, so the schema fully documents all 5 parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples, format details, or constraints). This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and the resource ('a new note in Bear'), making the purpose immediately obvious. It distinguishes itself from siblings like 'add_text' or 'add_tags' by being the primary creation tool rather than a modification tool.

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., Bear app must be running), when not to use it (e.g., for updating existing notes), or direct alternatives among siblings like 'add_text' for appending to notes.

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