Skip to main content
Glama

bear_list_todos

Read-onlyIdempotent

Find Bear notes with incomplete TODO items and retrieve title, tags, and completion counts.

Instructions

List Bear notes that have incomplete TODO items (markdown checkboxes like '- [ ]'). Returns each note's title, tags, and counts of complete/incomplete items.

Input Schema

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

Implementation Reference

  • Tool handler definition for bear_list_todos. Defines the tool metadata (name, description, input schema with optional limit parameter) and the buildArgs function that constructs CLI arguments ["todo", "--json", optionally "--limit", N] to pass to the external bcli binary.
    bear_list_todos: {
      tool: {
        name: "bear_list_todos",
        description:
          "List Bear notes that have incomplete TODO items (markdown checkboxes like '- [ ]'). Returns each note's title, tags, and counts of complete/incomplete items.",
        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 = ["todo", "--json"];
        if (input.limit) args.push("--limit", String(input.limit));
        return args;
      },
    },
  • The 'tools' registry object that maps tool names (like 'bear_list_todos') to their ToolHandler definitions. This is imported by index.ts where it's used for ListToolsRequestSchema and CallToolRequestSchema.
    export const tools: Record<string, ToolHandler> = {
  • Registration of bear_list_todos as an MCP tool. The server exposes all tools (including bear_list_todos) via ListToolsRequestSchema, and dispatches calls via CallToolRequestSchema which looks up the handler by name.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: Object.values(tools).map((t) => t.tool),
    }));
  • Helper that executes the bcli CLI binary with automatic re-authentication on auth errors. The bear_list_todos handler's buildArgs produces args that are passed to this function.
    export async function execBcliWithReauth(
      args: string[],
    ): Promise<{ stdout: string; stderr: string }> {
      try {
        return await execBcli(args);
      } catch (error) {
        if (error instanceof AuthError) {
          await performReauth();
          return await execBcli(args);
        }
        throw error;
      }
    }
Behavior3/5

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

Annotations already indicate readOnlyHint, destructiveHint, and idempotentHint, making the safe nature clear. The description adds return field details (title, tags, counts) but does not disclose sorting, pagination, or behavior when no incomplete TODOs exist. This adds some context but not extensive behavioral insight.

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?

Description is a single, well-structured sentence that front-loads the purpose and includes return details. Every word contributes meaning, with no redundancy or tangential information.

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 adequately explains the filtering logic and return fields. With annotations covering safety and idempotency, no additional completeness is needed.

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 single parameter (limit) is fully documented in the input schema with a clear description. The tool description does not reference the parameter or add any additional semantics, so baseline of 3 applies per the rule.

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?

Description clearly states the tool lists Bear notes with incomplete TODO items, specifying the markdown checkbox format. It distinguishes from siblings like bear_list_notes (all notes) and bear_get_todos (specific note's todos) by focusing on incomplete items across notes.

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?

Description implies usage for finding notes with incomplete TODOs but does not explicitly state when to use it over alternatives like bear_get_todos or bear_list_notes. No exclusion criteria or alternative tools are mentioned.

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