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;
      },
    },
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds important behavioral details: tag CloudKit index behavior, locked note indicator, and the effect of the 'raw' option. No contradiction with annotations.

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 four sentences long, each serving a distinct purpose: stating the action, listing return values, explaining special flags, and describing an option. No redundant or irrelevant 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?

Given no output schema, the description adequately explains return values (title, tags, markdown, dates) and handles edge cases (locked notes, raw option). It is complete for the tool's functionality.

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 already covers 100% of parameters, but the description adds extra meaning for 'raw' (explains it returns only markdown without metadata) and clarifies 'id' as uniqueIdentifier. This goes beyond the schema descriptions.

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 verb 'Get', the resource 'a single Bear note's full content and metadata', and the method 'by ID'. It differentiates from sibling tools like bear_list_notes and bear_search by focusing on individual note retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a specific note ID is known, but it does not explicitly state when not to use or mention alternatives. However, given sibling names and context, it is clear enough for an agent.

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