Skip to main content
Glama

bear_archive_note

Idempotent

Archive a Bear note to hide it from the main list; use undo to unarchive.

Instructions

Archive a Bear note. Archived notes are hidden from the main list but not deleted. Use 'undo' to unarchive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNote ID (uniqueIdentifier)
undoNoUnarchive the note instead of archiving

Implementation Reference

  • The handler function that builds CLI arguments for the bear_archive_note tool. It calls the 'archive' subcommand with the note ID and optional '--undo' flag.
    buildArgs: (input) => {
      const args = ["archive", String(input.id), "--json"];
      if (input.undo) args.push("--undo");
      return args;
    },
  • The tool definition and input schema for bear_archive_note. Accepts an 'id' (required) and an optional 'undo' boolean. Marked idempotent.
    bear_archive_note: {
      tool: {
        name: "bear_archive_note",
        description:
          "Archive a Bear note. Archived notes are hidden from the main list but not deleted. Use 'undo' to unarchive.",
        inputSchema: {
          type: "object" as const,
          properties: {
            id: {
              type: "string",
              description: "Note ID (uniqueIdentifier)",
            },
            undo: {
              type: "boolean",
              description: "Unarchive the note instead of archiving",
            },
          },
          required: ["id"],
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
  • Registration in index.ts: the CallToolRequestHandler dispatches to the tool by name from the tools record, which includes bear_archive_note.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: input } = request.params;
      const handler = tools[name];
  • Registration in index.ts: the ListToolsRequestSchema handler exposes all tools (including bear_archive_note) to the MCP client.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: Object.values(tools).map((t) => t.tool),
    }));
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds value beyond annotations by specifying that notes are not deleted and can be unarchived. It aligns with non-destructive and idempotent hints.

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?

Two concise sentences, front-loaded with the action, with no unnecessary words. Efficient and clear.

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

Completeness4/5

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

The description covers the core behavior and reversibility. Though there is no output schema, the action is simple and the explanation is adequate for the agent.

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 coverage is 100%, so parameters are already documented. The description does not add significant additional meaning beyond the schema's field descriptions.

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

Purpose5/5

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

The description clearly states the action 'Archive a Bear note' and explains the effect: hidden but not deleted. It distinguishes from deletion and mentions the undo feature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides guidance on using the undo parameter to unarchive, but does not explicitly compare with sibling tools like bear_trash_note or indicate when not to use this tool.

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/mreider/better-bear'

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