Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager

bear_get_untagged

Retrieve notes without tags from Bear App to organize and manage untagged content efficiently.

Instructions

Get untagged notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch term
tokenNoBear API token
show_windowNoShow Bear window

Implementation Reference

  • The handler function that implements the core logic for the 'bear_get_untagged' tool. It constructs parameters from input args, calls Bear's 'untagged' x-callback-url via executeWithCallback, processes the returned data, and formats it as MCP content.
    private async getUntagged(args: any) {
      const params: Record<string, string | boolean> = {};
      
      if (args.search) params.search = args.search;
      if (args.token) params.token = args.token;
      if (args.show_window) params.show_window = "yes";
    
      const untaggedData = await this.executeWithCallback("untagged", params);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              message: `Retrieved untagged notes${args.search ? ` matching: ${args.search}` : ""}`,
              notes: untaggedData
            }, null, 2)
          }
        ]
      };
    }
  • Input schema definition for the 'bear_get_untagged' tool, specifying optional properties for search term, API token, and window visibility.
    {
      name: "bear_get_untagged",
      description: "Get untagged notes",
      inputSchema: {
        type: "object",
        properties: {
          search: {
            type: "string",
            description: "Search term"
          },
          token: {
            type: "string",
            description: "Bear API token"
          },
          show_window: {
            type: "boolean",
            description: "Show Bear window"
          }
        }
      }
    },
  • src/index.ts:723-724 (registration)
    Switch case registration that maps the tool name 'bear_get_untagged' to its handler function within the CallToolRequestSchema handler.
    case "bear_get_untagged":
      return await this.getUntagged(args);
  • src/index.ts:550-570 (registration)
    Tool registration in the ListToolsRequestSchema response, including name, description, and schema.
    {
      name: "bear_get_untagged",
      description: "Get untagged notes",
      inputSchema: {
        type: "object",
        properties: {
          search: {
            type: "string",
            description: "Search term"
          },
          token: {
            type: "string",
            description: "Bear API token"
          },
          show_window: {
            type: "boolean",
            description: "Show Bear window"
          }
        }
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Get untagged notes' implies a read-only operation but doesn't specify whether it returns all untagged notes, supports pagination, requires authentication (though the 'token' parameter hints at this), or has any rate limits. The description lacks crucial context about how the tool behaves beyond its basic function.

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 at three words, with zero wasted language. It's front-loaded with the core purpose, though this brevity comes at the cost of completeness. Every word earns its place by directly stating the tool's function without redundancy.

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 moderate complexity (3 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain the return format (e.g., list of notes, error handling), how results are structured, or interaction with sibling tools. For a retrieval tool with authentication and display parameters, more context is needed to guide effective use.

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%, with all three parameters ('search', 'token', 'show_window') documented in the schema. The description adds no additional meaning about parameters beyond what the schema provides, such as explaining how 'search' interacts with untagged filtering or what 'show_window' visually does. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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 untagged notes' clearly states the verb ('Get') and resource ('untagged notes'), providing basic purpose. However, it doesn't distinguish this tool from similar sibling tools like 'bear_search' or 'bear_get_tags', leaving ambiguity about its specific scope within the note retrieval family.

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 offers no guidance on when to use this tool versus alternatives. With siblings like 'bear_search' (general search), 'bear_get_tags' (get tags), and 'bear_get_today' (get today's notes), there's no indication of when untagged notes retrieval is preferred over other filtering methods or what prerequisites might exist.

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/bigjeager/bear-mcp-server'

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