Skip to main content
Glama

get_archived_notes

Retrieve all archived notes from Bear Notes on macOS to access and manage previously stored content through the MCP Bear server.

Instructions

Get all archived notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_archived_notes function, which queries the ZSFNOTE table for entries where ZARCHIVED=1.
    def get_archived_notes() -> list[dict[str, Any]]:
        """
        Retrieve all archived notes from Bear.
    
        Returns:
            List of archived notes
        """
        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=1;")
            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()
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. It states 'Get all archived notes', which implies a read-only operation, but doesn't disclose behavioral traits such as pagination, rate limits, authentication needs, or what happens if no archived notes exist. The description is minimal and lacks critical context for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence 'Get all archived notes', which is front-loaded and wastes no words. However, it's arguably too concise—it could benefit from a bit more detail (e.g., on scope or behavior) without becoming verbose, slightly reducing efficiency.

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 complexity (a retrieval tool with siblings), no annotations, and no output schema, the description is incomplete. It doesn't explain what 'all' means, how results are returned, or any limitations. For a tool in a note-taking context with multiple alternatives, more guidance on usage and output is needed.

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% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate here. Baseline is 4 for zero parameters, as there's nothing to compensate for and the schema fully covers the absence of inputs.

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

Purpose3/5

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

The description 'Get all archived notes' clearly states the action (get) and resource (archived notes), but it's vague about scope—does 'all' mean all archived notes globally, or within a workspace/user context? It distinguishes from siblings like 'get_notes' (non-archived) and 'unarchive_note', but lacks specificity on filtering or ordering.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this should be used instead of 'get_notes' with a filter, or when 'search_bear' might be more appropriate for finding specific archived notes. The description implies usage for retrieving archived notes but offers no exclusions or prerequisites.

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