Skip to main content
Glama

bear_get_note

Read-onlyIdempotent

Retrieve a Bear note's full content, metadata, tags, and dates by its ID. Optionally get only the raw markdown without metadata.

Instructions

Get a single Bear note's full content and metadata by ID. Returns the note title, tags, full markdown text, and dates. The response includes 'tags' (CloudKit index, may contain ancestor tags like 'parent' for a note tagged '#parent/child') and 'attached_tags' (leaves only). If the note is locked/private, 'locked: true' will be included in the response. Use the 'raw' option to get just the markdown without metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNote ID (uniqueIdentifier)
rawNoReturn only the raw markdown content

Implementation Reference

  • Input schema for bear_get_note: requires 'id' (string) and optional 'raw' (boolean).
    inputSchema: {
      type: "object" as const,
      properties: {
        id: {
          type: "string",
          description: "Note ID (uniqueIdentifier)",
        },
        raw: {
          type: "boolean",
          description: "Return only the raw markdown content",
        },
      },
      required: ["id"],
    },
  • buildArgs handler for bear_get_note: builds CLI args array ['get', <id>, '--json'] with optional '--raw' flag.
    buildArgs: (input) => {
      const args = ["get", String(input.id), "--json"];
      if (input.raw) args.push("--raw");
      return args;
    },
  • Registration of bear_get_note in the tools record with tool metadata (name, description, schema, annotations, buildArgs).
    bear_get_note: {
      tool: {
        name: "bear_get_note",
        description:
          "Get a single Bear note's full content and metadata by ID. Returns the note title, tags, full markdown text, and dates. The response includes 'tags' (CloudKit index, may contain ancestor tags like 'parent' for a note tagged '#parent/child') and 'attached_tags' (leaves only). If the note is locked/private, 'locked: true' will be included in the response. Use the 'raw' option to get just the markdown without metadata.",
        inputSchema: {
          type: "object" as const,
          properties: {
            id: {
              type: "string",
              description: "Note ID (uniqueIdentifier)",
            },
            raw: {
              type: "boolean",
              description: "Return only the raw markdown content",
            },
          },
          required: ["id"],
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => {
        const args = ["get", String(input.id), "--json"];
        if (input.raw) args.push("--raw");
        return args;
      },
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.26

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds critical details about locked notes behavior, tag vs attached_tags distinction, and raw option, going beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with main action, no redundant information. Could be slightly more concise but very clear.

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

Completeness4/5

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

Given the tool's simplicity (2 params, no output schema), the description adequately explains return contents and options. Could mention response structure more explicitly, but sufficient.

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?

Input schema covers both parameters with 100% description coverage. Description adds minimal extra meaning: clarifies raw option returns markdown without metadata, but schema already states that. Baseline of 3 is appropriate.

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?

Clearly states it retrieves a single note's full content and metadata by ID, listing specific fields returned. Does not explicitly differentiate from sibling tools like search or list_notes, but the purpose is specific enough.

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?

No guidance on when to use this tool versus alternatives like bear_search or bear_list_notes. No exclusions or prerequisites mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.