Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

bear_create_note

Create a new note in Bear with customizable title, content, tags, attachments, and display options to organize information efficiently.

Instructions

Create a new note in Bear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNote title
textNoNote content
tagsNoComma-separated list of tags
pinNoPin note to top of list
timestampNoPrepend current date and time
clipboardNoGet text from clipboard
fileNoFile path to add to note
filenameNoCustom filename for attached file
open_noteNoOpen note after creation
new_windowNoOpen in new window
floatNoFloat note window
show_windowNoShow Bear window
editNoPlace cursor in note editor
typeNoNote type
urlNoURL to include in note

Implementation Reference

  • src/index.ts:781-813 (handler)
    The main handler function for the 'bear_create_note' tool. It maps input arguments to Bear URL parameters, executes the 'create' action via callback, and returns the note data.
    private async createNote(args: any) {
  const params: Record<string, string | boolean> = {};
  
  if (args.title) params.title = args.title;
  if (args.text) params.text = args.text;
  if (args.tags) params.tags = args.tags;
  if (args.pin) params.pin = "yes";
  if (args.timestamp) params.timestamp = "yes";
  if (args.clipboard) params.clipboard = "yes";
  if (args.file) params.file = args.file;
  if (args.filename) params.filename = args.filename;
  if (args.open_note) params.open_note = "yes";
  if (args.new_window) params.new_window = "yes";
  if (args.float) params.float = "yes";
  if (args.show_window) params.show_window = "yes";
  if (args.edit) params.edit = "yes";
  if (args.type) params.type = args.type;
  if (args.url) params.url = args.url;

  const noteData = await this.executeWithCallback("create", params);

  return {
    content: [
      {
        type: "text",
        text: JSON.stringify({
          message: `Created new note in Bear${args.title ? ` with title: ${args.title}` : ""}`,
          note: noteData
        }, null, 2)
      }
    ]
  };
}
  • src/index.ts:255-323 (schema)
    The input schema defining parameters for the 'bear_create_note' tool, registered in the list of available tools.
    {
  name: "bear_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"
      },
      tags: {
        type: "string",
        description: "Comma-separated list of tags"
      },
      pin: {
        type: "boolean",
        description: "Pin note to top of list"
      },
      timestamp: {
        type: "boolean",
        description: "Prepend current date and time"
      },
      clipboard: {
        type: "boolean",
        description: "Get text from clipboard"
      },
      file: {
        type: "string",
        description: "File path to add to note"
      },
      filename: {
        type: "string",
        description: "Custom filename for attached file"
      },
      open_note: {
        type: "boolean",
        description: "Open note after creation"
      },
      new_window: {
        type: "boolean",
        description: "Open in new window"
      },
      float: {
        type: "boolean",
        description: "Float note window"
      },
      show_window: {
        type: "boolean",
        description: "Show Bear window"
      },
      edit: {
        type: "boolean",
        description: "Place cursor in note editor"
      },
      type: {
        type: "string",
        description: "Note type"
      },
      url: {
        type: "string",
        description: "URL to include in note"
      }
    }
  }
},
  • src/index.ts:707-708 (registration)
    Switch case registration that dispatches 'bear_create_note' tool calls to the createNote handler method.
    case "bear_create_note":
  return await this.createNote(args);

Tool Definition Quality

C2.9/5.0
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 but offers minimal information. 'Create a new note' implies a write/mutation operation, but the description doesn't address permissions, side effects, error conditions, or what happens when parameters conflict (e.g., both 'text' and 'clipboard' specified). For a mutation tool with 15 parameters, this is inadequate.

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 maximally concise - a single sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration. It's appropriately sized for a tool whose complexity is captured in the detailed input schema.

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 15 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the return value, error conditions, or how parameters interact. While the schema documents individual parameters, the description fails to provide the holistic context needed for effective tool 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 each parameter is documented in the schema itself. The description adds no additional parameter information beyond the basic purpose statement. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('Create') and resource ('new note in Bear'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar siblings like bear_add_text or bear_grab_url, which also create notes through different mechanisms.

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 siblings like bear_add_text (adds text to existing notes), bear_grab_url (creates notes from URLs), and bear_add_file (adds files to notes), the agent receives no help in selecting the appropriate tool for different note-creation scenarios.

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