Skip to main content
Glama

bear_get_tags

Read-onlyIdempotent

Retrieve the full tag hierarchy from Bear, including note counts and pin status, to understand how notes are organized.

Instructions

Get the full tag hierarchy from Bear. Returns all tags with their note counts and pin status. Useful for understanding how notes are organized.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'bear_get_tags' tool handler definition in the tools registry. The buildArgs function generates args ['tags', '--json'] which calls the 'bcli' CLI with the 'tags' subcommand to fetch the full tag hierarchy from Bear. No input parameters are required.
    bear_get_tags: {
      tool: {
        name: "bear_get_tags",
        description:
          "Get the full tag hierarchy from Bear. Returns all tags with their note counts and pin status. Useful for understanding how notes are organized.",
        inputSchema: {
          type: "object" as const,
          properties: {},
        },
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      buildArgs: () => ["tags", "--json"],
    },
  • Input schema for bear_get_tags — defines 'name', 'description', and an empty 'inputSchema' (no parameters required).
    name: "bear_get_tags",
    description:
      "Get the full tag hierarchy from Bear. Returns all tags with their note counts and pin status. Useful for understanding how notes are organized.",
    inputSchema: {
      type: "object" as const,
      properties: {},
  • Tools are registered with the MCP server via ListToolsRequestSchema, which extracts all tool definitions from the tools object (including bear_get_tags).
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: Object.values(tools).map((t) => t.tool),
    }));
  • CallToolRequestSchema handler looks up tools by name (including 'bear_get_tags') from the tools registry and dispatches to buildArgs + bcli execution.
    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?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that the tool returns tag hierarchy with note counts and pin status, which is beyond the annotations, but no further behavioral details are needed.

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 two sentences long, front-loaded with the action ('Get the full tag hierarchy'), and every sentence adds value without redundancy.

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 parameters, no output schema, and comprehensive annotations, the description fully explains what the tool does and returns, making it complete for selection and invocation.

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 (0 parameters), so the baseline is 4. No additional parameter info is needed, and the description does not need to add anything.

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 'Get the full tag hierarchy from Bear' with specific outputs: all tags with note counts and pin status. This distinguishes it from sibling tools like bear_add_tag or 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 says 'Useful for understanding how notes are organized', which provides a general usage context but lacks explicit guidance on when not to use or alternatives.

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