Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager

bear_get_today

Retrieve today's notes from Bear App using search filters and API authentication to access daily content.

Instructions

Get today's notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch term
tokenNoBear API token
show_windowNoShow Bear window

Implementation Reference

  • The main handler function for the 'bear_get_today' tool. It constructs parameters from input arguments (search, token, show_window), calls the shared executeWithCallback method with action 'today', and returns a formatted content block with the retrieved notes.
    private async getToday(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 todayData = await this.executeWithCallback("today", params);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              message: `Retrieved today's notes${args.search ? ` matching: ${args.search}` : ""}`,
              notes: todayData
            }, null, 2)
          }
        ]
      };
    }
  • Input schema defining the parameters for the bear_get_today tool: optional search (string), token (string), and show_window (boolean).
    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:592-612 (registration)
    Registration of the bear_get_today tool in the MCP server's tools list, including name, description, and input schema.
    {
      name: "bear_get_today",
      description: "Get today's 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:727-728 (registration)
    Switch case that registers and dispatches execution of the bear_get_today tool to its handler method.
    case "bear_get_today":
      return await this.getToday(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 today's notes' implies a read-only operation, but it doesn't specify whether this requires authentication (though the 'token' parameter hints at it), what the return format is, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly, which is ideal for conciseness in tool descriptions.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'today's notes' means (e.g., creation date, modification date), the return format, or how parameters like 'search' interact with the date filter. For a tool with 3 parameters and no structured behavioral hints, more context 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 input schema has 100% description coverage, so all parameters ('search', 'token', 'show_window') are documented in the schema. The description adds no additional meaning beyond implying a date-based filter ('today's'), which isn't detailed in the schema. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get today's notes' clearly states the verb ('Get') and resource ('today's notes'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'bear_search' or 'bear_get_todo', which also retrieve notes with different filters, so it doesn't reach the highest clarity level.

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. It doesn't mention when to choose 'bear_get_today' over 'bear_search' or 'bear_get_todo', nor does it specify any prerequisites or exclusions, leaving the agent with minimal 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