Skip to main content
Glama

unarchive_note

Restore archived notes in Bear Notes on macOS by providing the note identifier, making previously hidden content accessible again.

Instructions

Unarchive a note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYesThe unique identifier of the note (ZUNIQUEIDENTIFIER)

Implementation Reference

  • The 'unarchive_note' function implements the logic to unarchive a note by calling the Bear x-callback-url 'unarchive'.
    def unarchive_note(note_id: str) -> dict[str, str]:
        """
        Unarchive a note.
    
        Args:
            note_id: The unique identifier of the note (ZUNIQUEIDENTIFIER)
    
        Returns:
            Dictionary with operation result
        """
        params = {"id": note_id}
    
        query_string = urllib.parse.urlencode(params)
        url = f"bear://x-callback-url/unarchive?{query_string}"
    
        return _open_bear_url(url)
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. 'Unarchive' implies a state change (from archived to active), but it doesn't specify permissions required, side effects, error conditions, or what happens if the note isn't archived. This leaves critical behavioral traits undocumented.

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 extremely concise—three words—with zero wasted language. It's front-loaded and directly states the tool's function without unnecessary elaboration, making it highly efficient for quick comprehension.

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 tool's mutation nature (state change) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like success/failure responses, side effects, or prerequisites, leaving significant gaps for an agent to understand the tool fully.

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 the 'note_id' parameter. The description adds no additional meaning beyond implying the note must be archived, but this is minimal value. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 ('unarchive') and resource ('a note'), making the tool's purpose immediately understandable. It distinguishes from siblings like 'archive_note' by specifying the opposite operation. However, it doesn't explicitly mention what system or context the note belongs to, which slightly limits specificity.

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., the note must be archived first), exclusions, or related tools like 'archive_note' or 'trash_note', leaving usage context entirely implicit.

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