Skip to main content
Glama

Get Notes

keychain_get_notes
Read-only

Retrieve secure notes from a Bitwarden vault by searching with a specific term, enabling access to stored information while maintaining security.

Instructions

Get item notes by search term (bw get notes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes
revealNo

Implementation Reference

  • The handler for keychain_get_notes (registered as .get_notes) which calls sdk.getNotes.
      `${deps.toolPrefix}.get_notes`,
      {
        title: 'Get Notes',
        description: 'Get item notes by search term (bw get notes).',
        annotations: { readOnlyHint: true },
        inputSchema: {
          term: z.string(),
          reveal: z.boolean().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const notes = await sdk.getNotes(
          { term: input.term },
          { reveal: effectiveReveal(input) },
        );
        return {
          structuredContent: toolResult('notes', notes.value, notes.revealed),
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior3/5

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

The annotation 'readOnlyHint: true' already indicates this is a safe read operation. The description adds minimal behavioral context beyond this - it mentions searching by term but doesn't describe what 'reveal' parameter does, how results are returned, or any limitations. No contradiction with annotations exists.

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

Conciseness3/5

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

The description is brief (one sentence plus parenthetical), but the parenthetical '(bw get notes)' adds no value for an AI agent and wastes space. The core description is front-loaded but could be more efficiently structured to explain both parameters.

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

Completeness2/5

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

For a search/retrieval tool with 2 parameters (one undocumented), no output schema, and minimal annotations, the description is inadequate. It doesn't explain what 'item notes' are, how results are structured, what the 'reveal' parameter controls, or how this differs from other search/retrieval tools in the sibling list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, both parameters are undocumented in the schema. The description only mentions 'search term' which corresponds to the 'term' parameter, leaving the 'reveal' parameter completely unexplained. This fails to compensate for the schema's lack of documentation.

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?

The description clearly states the action ('Get') and resource ('item notes'), specifying it's done 'by search term'. It distinguishes from siblings like 'keychain_get_item' by focusing specifically on notes. However, it doesn't fully clarify what 'item notes' means in this context (notes within items vs. note items).

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 is provided on when to use this tool versus alternatives like 'keychain_search_items' or 'keychain_get_item'. The description mentions a search term but doesn't explain whether this is the primary search method for notes or if there are other options. The parenthetical '(bw get notes)' appears to reference a CLI command but doesn't help the AI 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/icoretech/warden-mcp'

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