Skip to main content
Glama
maxim-ist

MCP Bear

by maxim-ist
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

archive_note

Archive notes in Bear Notes on macOS by moving them to the archive folder, helping users organize and declutter their workspace.

Instructions

Archive a note

Input Schema

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

Implementation Reference

  • src/mcp_bear/bear_url.py:183-198 (handler)
    The core handler function that constructs the x-callback-url for Bear to archive a note.
    def archive_note(note_id: str) -> dict[str, str]:
    """
    Archive 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/archive?{query_string}"

    return _open_bear_url(url)
  • src/mcp_bear/server.py:237-250 (registration)
    Tool definition and registration within the MCP server.
    Tool(
    name="archive_note",
    description="Archive a note",
    inputSchema={
        "type": "object",
        "properties": {
            "note_id": {
                "type": "string",
                "description": "The unique identifier of the note (ZUNIQUEIDENTIFIER)",
            },
        },
        "required": ["note_id"],
    },
),

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, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't explain what archiving does (e.g., moves note to archive, hides it from default views, requires permissions, or if it's reversible). This leaves critical gaps for a mutation tool.

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 with just three words, front-loaded and zero waste. It efficiently conveys the core action without unnecessary detail, though this brevity contributes to gaps in other dimensions.

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 no annotations and no output schema, the description is incomplete. It doesn't cover what archiving entails, success/failure behavior, return values, or how it differs from siblings like 'trash_note'. Given the complexity and lack of structured data, more context 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 100% description coverage, so the schema fully documents the single parameter 'note_id'. The description adds no parameter semantics beyond implying 'note_id' is needed, which is minimal but acceptable given high schema coverage. Baseline is 3, but with zero parameters explained in description and only one parameter total, it slightly exceeds minimum.

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 'Archive a note' clearly states the action (archive) and resource (note), but it's vague about what archiving entails and doesn't differentiate from sibling tools like 'trash_note' or 'unarchive_note'. It provides basic purpose but lacks specificity about scope or effect.

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 like 'trash_note' or 'unarchive_note'. The description doesn't mention prerequisites, such as whether the note must be unarchived first, or context for choosing archiving over other operations.

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