Skip to main content
Glama

bear_find_untagged

Read-onlyIdempotent

Find Bear notes that have no tags assigned. Identify untagged notes to organize or tag them.

Instructions

List Bear notes that have no tags assigned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of notes to return (default 30)

Implementation Reference

  • The 'bear_find_untagged' tool is registered in the tools map with its tool definition (name, description, inputSchema, annotations) and buildArgs function that constructs the bcli command 'ls --untagged --json' with an optional limit parameter.
    bear_find_untagged: {
      tool: {
        name: "bear_find_untagged",
        description:
          "List Bear notes that have no tags assigned.",
        inputSchema: {
          type: "object" as const,
          properties: {
            limit: {
              type: "number",
              description: "Maximum number of notes to return (default 30)",
            },
          },
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => {
        const args = ["ls", "--untagged", "--json"];
        if (input.limit) args.push("--limit", String(input.limit));
        return args;
      },
    },
  • The generic request handler for all tools (including 'bear_find_untagged') in index.ts's CallToolRequestSchema handler. It looks up the tool by name from the tools map, calls buildArgs, runs the bcli command, and parses JSON output.
      server.setRequestHandler(CallToolRequestSchema, async (request) => {
        const { name, arguments: input } = request.params;
        const handler = tools[name];
    
        if (!handler) {
          return {
            content: [{ type: "text", text: `Unknown tool: ${name}` }],
            isError: true,
          };
        }
    
        const params = (input ?? {}) as Record<string, unknown>;
    
        // Validate bear_edit_note: need at least one edit operation
        if (name === "bear_edit_note") {
          const hasAppend = params.append_text !== undefined;
          const hasBody = params.body !== undefined;
          const hasSetFm = params.set_frontmatter !== undefined &&
            Object.keys(params.set_frontmatter as object).length > 0;
          const hasRemoveFm = Array.isArray(params.remove_frontmatter) &&
            (params.remove_frontmatter as unknown[]).length > 0;
          const hasFm = hasSetFm || hasRemoveFm;
    
          if (!hasAppend && !hasBody && !hasFm) {
            return {
              content: [
                {
                  type: "text",
                  text: "Provide 'append_text', 'body', 'set_frontmatter', or 'remove_frontmatter'.",
                },
              ],
              isError: true,
            };
          }
          if (hasAppend && hasBody) {
            return {
              content: [
                {
                  type: "text",
                  text: "Provide either 'append_text' or 'body', not both.",
                },
              ],
              isError: true,
            };
          }
        }
    
        try {
          const args = handler.buildArgs(params);
          let result: { stdout: string; stderr: string };
    
          // Check if this tool needs stdin piping
          const stdinData = handler.usesStdin?.(params) ?? null;
          if (stdinData !== null) {
            result = await execBcliWithStdinAndReauth(args, stdinData);
          } else {
            result = await execBcliWithReauth(args);
          }
    
          // Parse JSON output from bcli
          const stdout = result.stdout.trim();
          if (!stdout) {
            return {
              content: [{ type: "text", text: "Command completed successfully." }],
            };
          }
    
          // Validate it's JSON and pretty-print
          try {
            const parsed = JSON.parse(stdout);
            return {
              content: [
                { type: "text", text: JSON.stringify(parsed, null, 2) },
              ],
            };
          } catch {
            // If bcli returned non-JSON, pass it through
            return {
              content: [{ type: "text", text: stdout }],
            };
          }
        } catch (error) {
          const message =
            error instanceof BcliError ? error.message : String(error);
          return {
            content: [{ type: "text", text: message }],
            isError: true,
          };
        }
      });
    
      return server;
    }
    
    // Smithery sandbox: allows tool scanning without bcli installed
    export function createSandboxServer(): Server {
      return createServer();
    }
    
    // Default export for Smithery
    export default createServer;
    
    // Direct execution: connect via stdio
    const isDirectRun = process.argv[1]?.endsWith("index.js") ||
      process.argv[1]?.endsWith("better-bear") ||
      process.argv[1]?.endsWith("better-bear-mcp");
    
    if (isDirectRun) {
      const server = createServer();
      const transport = new StdioServerTransport();
      server.connect(transport).catch((error) => {
        console.error("Fatal error:", error);
        process.exit(1);
      });
    }
  • The input schema for bear_find_untagged defines an optional 'limit' parameter (number) with a default of 30 notes.
    inputSchema: {
      type: "object" as const,
      properties: {
        limit: {
          type: "number",
          description: "Maximum number of notes to return (default 30)",
        },
      },
    },
Behavior3/5

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

Annotations already indicate read-only safety. The description adds no additional behavioral context beyond listing untagged notes.

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?

Single clear sentence with no unnecessary words, perfectly front-loaded.

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?

Simple tool with one optional param and annotations. It adequately explains purpose, though it could hint at output format.

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% and describes the limit parameter. The description does not add meaning beyond the schema, so baseline 3.

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 tool lists notes with no tags, which is a specific verb+resource. It distinguishes from siblings like bear_list_notes (all notes) and bear_search (text search).

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

Usage Guidelines3/5

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

The description implies use when wanting untagged notes but does not explicitly state when to use or avoid this tool, nor mention alternatives.

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

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