Skip to main content
Glama

Replace Note Content

bear-replace-text
DestructiveIdempotent

Replace text in a Bear note — full body or a specific section under a header. Get the note ID via search first. Requires content replacement enabled.

Instructions

Replace content in an existing Bear note — either the full body or a specific section. Requires content replacement to be enabled in settings. Use bear-search-notes first to get the note ID. To add text without replacing existing content use bear-add-text instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNote identifier (ID) from bear-search-notes
scopeYesReplacement target: 'section' replaces under a specific header (requires header), 'full-note-body' replaces the entire note body (header must not be set)
textYesReplacement text content. When scope is "section", provide only the direct content for the targeted header — do not include markdown sub-headers (###). Replace sub-sections with separate calls targeting each sub-header.
headerNoSection header to target — required when scope is "section", forbidden when scope is "full-note-body". Accepts any heading level, including the note title (H1).
Behavior4/5

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

Annotations already indicate destructive and idempotent; description adds context about required setting and replacement behavior. No contradictions.

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?

Three concise sentences, front-loaded with purpose, followed by prerequisites and alternative. No unnecessary words.

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?

Covers prerequisites, usage order, and scoping details. Lacks return value info, but annotations and schema compensate for moderate completeness.

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?

Schema covers all 4 params with descriptions; description adds minimal extra context (e.g., getting ID from bear-search-notes). Baseline 3 due to high coverage.

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?

Description clearly states 'Replace content in an existing Bear note' with two scope options, distinguishing from siblings like bear-add-text.

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

Usage Guidelines5/5

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

Explicitly mentions required setting, prerequisite step (bear-search-notes), and alternative tool (bear-add-text).

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/vasylenko/bear-notes-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server