Skip to main content
Glama

bear_find_untagged

Read-onlyIdempotent

Find Bear notes without tags by listing up to 30 unlabeled notes, helping you organize and tag untagged content.

Instructions

List Bear notes that have no tags assigned.

Input Schema

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

Implementation Reference

  • buildArgs function for bear_find_untagged: builds CLI args ['ls', '--untagged', '--json'] with optional --limit flag. This is the logic that executes when the tool is called.
      buildArgs: (input) => {
        const args = ["ls", "--untagged", "--json"];
        if (input.limit) args.push("--limit", String(input.limit));
        return args;
      },
    },
  • Tool definition and input schema for bear_find_untagged. Accepts an optional 'limit' number (default 30). Annotated as readOnly, non-destructive, and idempotent.
    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,
        },
      },
  • Tools are registered via ListToolsRequestSchema handler which iterates all tools including bear_find_untagged.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: Object.values(tools).map((t) => t.tool),
    }));
  • CallToolRequestSchema handler dispatches to bear_find_untagged via the tools[name] lookup, then calls buildArgs to construct CLI arguments.
    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,
        };
      }
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description does not add further behavioral context beyond the tool's purpose, which is acceptable given the safety info already present.

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 a single sentence, directly stating the tool's purpose with no unnecessary words. It is front-loaded and efficient.

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

Completeness5/5

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

For a simple list tool with one optional parameter and no output schema, the description fully covers the needed information. The annotations complement it.

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?

The schema covers the single parameter (limit) with description, so the description adds no additional meaning. Baseline 3 is appropriate.

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 (List) and the specific resource (Bear notes with no tags). It is distinct from sibling tools like bear_list_notes (all notes) and bear_search (by query).

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 usage for untagged notes but does not explicitly state when to use this over alternatives or provide exclusions. Siblings are present but no guidance is given.

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