Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager

bear_get_todo

Retrieve todo notes from Bear App using search terms, API tokens, and window display options to organize tasks.

Instructions

Get todo notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch term
tokenNoBear API token
show_windowNoShow Bear window

Implementation Reference

  • The main handler function for 'bear_get_todo' tool. It constructs parameters from input args, calls Bear's 'todo' x-callback via executeWithCallback, and returns a formatted response with todo notes.
    private async getTodo(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 todoData = await this.executeWithCallback("todo", params);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              message: `Retrieved todo notes${args.search ? ` matching: ${args.search}` : ""}`,
              notes: todoData
            }, null, 2)
          }
        ]
      };
  • Input schema definition for the 'bear_get_todo' tool, registered in the ListTools response.
    {
      name: "bear_get_todo",
      description: "Get todo 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:725-726 (registration)
    Switch case in CallToolRequestSchema handler that dispatches to the getTodo method for 'bear_get_todo'.
    case "bear_get_todo":
      return await this.getTodo(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get todo notes' implies a read-only operation but doesn't specify whether it returns a list, details permissions needed, mentions rate limits, or describes the return format. For a tool with 3 parameters and no annotation coverage, this is a significant gap in transparency.

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 action and resource, making it efficient and easy to parse, though this brevity comes at the cost of detail.

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 complexity (3 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'todo notes' are, how results are returned, or provide any behavioral context, leaving the agent with insufficient information to use the tool effectively beyond basic inference.

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 description adds no meaning beyond what the input schema provides, as it doesn't mention any parameters. However, with 100% schema description coverage, the baseline is 3, since the schema documents 'search' (search term), 'token' (API token), and 'show_window' (show Bear window) adequately, though the description doesn't compensate or enhance this.

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 todo notes' states the basic action (get) and resource (todo notes), which provides a minimal understanding of purpose. However, it lacks specificity about what 'todo notes' are in the Bear context and doesn't distinguish this tool from sibling tools like 'bear_search' or 'bear_get_today', making it vague rather than clearly differentiated.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'bear_search' (general search), 'bear_get_today' (today's notes), and 'bear_get_untagged' (untagged notes), there's no indication of whether this tool filters by todo status, retrieves all todos, or serves a specific use case, leaving the agent with no usage context.

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