Skip to main content
Glama

get_notes

Retrieve all notes from Bear Notes on macOS to access, search, and manage your content through the MCP Bear server interface.

Instructions

Get all notes from Bear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function 'get_notes' which queries the SQLite database for non-archived notes.
    def get_notes() -> list[dict[str, Any]]:
        """Retrieve all non-archived notes from Bear."""
        db_path = get_bear_db_path()
        conn = sqlite3.connect(db_path)
        conn.row_factory = sqlite3.Row
        cursor = conn.cursor()
    
        try:
            cursor.execute("SELECT * FROM ZSFNOTE WHERE ZARCHIVED=0;")
            rows = cursor.fetchall()
    
            notes = []
            for row in rows:
                notes.append({
                    "ZCREATIONDATE": row["ZCREATIONDATE"],
                    "ZSUBTITLE": row["ZSUBTITLE"],
                    "ZTEXT": row["ZTEXT"],
                    "ZTITLE": row["ZTITLE"],
                    "ZUNIQUEIDENTIFIER": row["ZUNIQUEIDENTIFIER"],
                })
    
            return notes
        finally:
            conn.close()
  • Registration of the 'get_notes' tool in the MCP server via the list_tools decorator.
    Tool(
        name="get_notes",
        description="Get all notes from Bear",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Call-site logic in the server's 'call_tool' handler that invokes 'get_notes' when requested.
    if name == "get_notes":
        notes = get_notes()
        return [TextContent(type="text", text=str({"notes": notes}))]
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 action ('Get all notes') but doesn't describe what 'Get' entails—such as whether it returns a list, the format of notes, pagination behavior, or any permissions required. This leaves significant gaps in understanding how the tool behaves in practice.

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 with zero waste—'Get all notes from Bear' directly conveys the core action without unnecessary words. It's front-loaded and appropriately sized for a simple tool, 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 lack of annotations and output schema, the description is incomplete for a tool that likely returns multiple notes. It doesn't explain what 'notes' consist of, how they're structured, or any limitations (e.g., number of notes returned). For a retrieval tool with no structured output guidance, more context is needed to help the agent use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% description coverage, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. This meets the baseline for tools with no parameters, as it doesn't mislead or omit necessary details.

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 ('Get') and resource ('all notes from Bear'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'get_notes_by_tag' or 'get_archived_notes', but the 'all notes' phrasing implies a comprehensive retrieval without filtering.

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_notes_by_tag' or 'get_archived_notes'. It lacks any mention of prerequisites, exclusions, or context for choosing this over sibling tools, leaving the agent to infer usage from the tool name 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