Skip to main content
Glama

bear_note_stats

Read-onlyIdempotent

Retrieve key statistics from your Bear notes library: total notes, words, tags, pinned, archived, trashed, TODOs, dates, and top tags.

Instructions

Get statistics about the Bear notes library: total notes, words, tags, pinned, archived, trashed, notes with TODOs, oldest/newest dates, and top 10 tags by note count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Input schema for bear_note_stats - no input parameters required (empty object)
    inputSchema: {
      type: "object" as const,
      properties: {},
    },
  • Full tool registration entry for bear_note_stats in the tools map. Defines the tool metadata (name, description, annotations) and buildArgs callback that builds CLI arguments ["stats", "--json"]. The handler is not a separate function - the registration itself contains the handler logic via buildArgs.
    bear_note_stats: {
      tool: {
        name: "bear_note_stats",
        description:
          "Get statistics about the Bear notes library: total notes, words, tags, pinned, archived, trashed, notes with TODOs, oldest/newest dates, and top 10 tags by note count.",
        inputSchema: {
          type: "object" as const,
          properties: {},
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: () => ["stats", "--json"],
    },
  • The tool registration includes buildArgs which generates CLI args ["stats", "--json"]. The actual execution of the bcli command with these args happens in index.ts (line 81-89) where handler.buildArgs(params) is called and the result is passed to execBcliWithReauth. No standalone handler function exists - the tool is fully defined by this entry.
    bear_note_stats: {
      tool: {
        name: "bear_note_stats",
        description:
          "Get statistics about the Bear notes library: total notes, words, tags, pinned, archived, trashed, notes with TODOs, oldest/newest dates, and top 10 tags by note count.",
        inputSchema: {
          type: "object" as const,
          properties: {},
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: () => ["stats", "--json"],
    },
Behavior3/5

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

Annotations already provide readOnlyHint (true), destructiveHint (false), and idempotentHint (true). The description adds that it returns statistics but does not disclose additional behavioral traits (e.g., caching, performance impact) beyond what annotations cover.

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, front-loaded with the purpose, and lists all returned stats efficiently. No redundant 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 no-parameter, read-only tool with annotations covering safety, the description is complete. It enumerates the exact statistics returned, so an agent knows what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameters, so schema coverage is 100%. The description does not need to add parameter info; it effectively describes the tool's output. Baseline 4 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 tool's purpose: 'Get statistics about the Bear notes library' and lists specific metrics (total notes, words, tags, etc.), making it distinct from sibling tools like bear_list_notes or bear_get_note.

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 retrieving summary statistics but does not explicitly state when to prefer this tool over alternatives or mention any exclusions. No guidance on when not to use it.

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