Skip to main content
Glama
netologist

Bear Notes MCP Server

by netologist

get_bear_note

Retrieve a specific note from Bear App using its unique identifier to access complete content and metadata.

Instructions

Get a specific Bear note by ID

Args: note_id: Bear note's unique identifier

Returns: Complete note content with metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYes

Implementation Reference

  • main.py:172-190 (handler)
    The main handler function for the 'get_bear_note' tool. Decorated with @mcp.tool() for registration. Retrieves a Bear note by ID using the helper function and returns it or an error message.
    @mcp.tool()
    def get_bear_note(note_id: str) -> Dict[str, Any]:
        """
        Get a specific Bear note by ID
        
        Args:
            note_id: Bear note's unique identifier
        
        Returns:
            Complete note content with metadata
        """
        try:
            note = get_note_by_id(note_id)
            if note:
                return note
            else:
                return {"error": "Note not found"}
        except Exception as e:
            return {"error": f"Error retrieving note: {str(e)}"}
  • Helper function that executes the core database query to fetch the Bear note by its unique ID from the SQLite database.
    def get_note_by_id(note_id: str) -> Optional[Dict[str, Any]]:
        """Get a specific note by ID"""
        conn = get_bear_db_connection()
        
        try:
            cursor = conn.execute("""
                SELECT 
                    ZUNIQUEIDENTIFIER as id,
                    ZTITLE as title,
                    ZTEXT as content,
                    ZCREATIONDATE as created_date,
                    ZMODIFICATIONDATE as modified_date
                FROM ZSFNOTE 
                WHERE ZUNIQUEIDENTIFIER = ? AND ZTRASHED = 0
            """, (note_id,))
            
            row = cursor.fetchone()
            if row:
                content = row["content"] or ""
                return {
                    "id": row["id"],
                    "title": row["title"] or "Untitled",
                    "content": content,
                    "created_date": row["created_date"],
                    "modified_date": row["modified_date"],
                    "word_count": len(content.split()) if content else 0
                }
            return None
            
        finally:
            conn.close()
  • main.py:19-26 (helper)
    Utility function to establish connection to the Bear App SQLite database.
    def get_bear_db_connection():
        """Connect to Bear database"""
        if not os.path.exists(BEAR_DB_PATH):
            raise FileNotFoundError(f"Bear database not found: {BEAR_DB_PATH}")
        
        conn = sqlite3.connect(BEAR_DB_PATH)
        conn.row_factory = sqlite3.Row  # Enable column name access
        return conn
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. It states the tool retrieves a note by ID and returns content with metadata, but lacks details on error handling (e.g., what happens if the ID is invalid), permissions, or rate limits. This is a significant gap for a retrieval tool with zero annotation coverage.

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 highly concise and well-structured, using clear sections for 'Args' and 'Returns' in just three sentences. Every sentence adds value without redundancy, making it easy to parse and front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic operation and parameter meaning but lacks details on behavioral aspects like errors or output structure, leaving gaps that could hinder effective use by an agent.

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 description adds meaningful context for the single parameter 'note_id' by specifying it as 'Bear note's unique identifier,' which clarifies its purpose beyond the schema's basic title. With 0% schema description coverage and only one parameter, this compensates well, though it doesn't detail format or constraints.

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 ('Get') and resource ('Bear note by ID'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'get_recent_notes' or 'search_bear_notes' beyond the ID-based retrieval, which prevents a perfect 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. It doesn't mention when to prefer this over sibling tools like 'get_recent_notes' or 'search_bear_notes', nor does it specify prerequisites such as needing a valid note ID, leaving usage context unclear.

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/netologist/mcp-bear-notes'

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