Skip to main content
Glama

bear_rename_tag

Idempotent

Rename a tag across all Bear notes, updating every note that contains the old tag.

Instructions

Rename a tag across all Bear notes. Every note containing the old tag will be updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
old_nameYesCurrent tag name (without #)
new_nameYesNew tag name (without #)

Implementation Reference

  • Definition of the 'bear_rename_tag' tool including its input schema (old_name, new_name), description, and annotations.
    bear_rename_tag: {
      tool: {
        name: "bear_rename_tag",
        description:
          "Rename a tag across all Bear notes. Every note containing the old tag will be updated.",
        inputSchema: {
          type: "object" as const,
          properties: {
            old_name: {
              type: "string",
              description: "Current tag name (without #)",
            },
            new_name: {
              type: "string",
              description: "New tag name (without #)",
            },
          },
          required: ["old_name", "new_name"],
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => [
        "tag",
        "rename",
        String(input.old_name),
        String(input.new_name),
        "--json",
      ],
  • buildArgs function that constructs the CLI arguments for renaming a tag using 'bcli tag rename <old_name> <new_name> --json'.
    buildArgs: (input) => [
      "tag",
      "rename",
      String(input.old_name),
      String(input.new_name),
      "--json",
    ],
  • Tool registration via ListToolsRequestSchema - all tools from tools.ts are listed to the MCP client.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: Object.values(tools).map((t) => t.tool),
    }));
  • CallToolRequestSchema handler that dispatches incoming tool calls by name, looking up the handler (including bear_rename_tag) from the tools record.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: input } = request.params;
      const handler = tools[name];
    
      if (!handler) {
        return {
          content: [{ type: "text", text: `Unknown tool: ${name}` }],
          isError: true,
        };
      }
Behavior4/5

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

The description adds behavioral context beyond annotations, specifying that the rename applies across all notes containing the old tag. Annotations already indicate it's not read-only and not destructive, but the description clarifies the bulk nature of the operation.

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 extremely concise at two sentences, with no unnecessary words. It is front-loaded and delivers the core functionality immediately.

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 simple operation with two well-documented parameters and no output schema, the description is fairly complete. It could mention error conditions (e.g., if the old tag doesn't exist), but overall it adequately covers the use case.

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% coverage with descriptions for both parameters. The tool description adds no additional meaning beyond what the schema provides, so a baseline score of 3 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 renames a tag across all Bear notes, using a specific verb and resource. This distinguishes it from sibling tools like bear_add_tag and bear_delete_tag.

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 does not explicitly state when to use this tool versus alternatives. Usage is implied by the name and purpose, but no guidance is provided on prerequisites or 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