Skip to main content
Glama

Get Username

keychain_get_username
Read-only

Retrieve login usernames from Bitwarden vaults by searching with a specific term, enabling secure credential access for AI agents.

Instructions

Get a login username by search term (bw get username).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes

Implementation Reference

  • The handler for the tool `get_username` which uses the keychain SDK to retrieve a username.
      `${deps.toolPrefix}.get_username`,
      {
        title: 'Get Username',
        description: 'Get a login username by search term (bw get username).',
        annotations: { readOnlyHint: true },
        inputSchema: {
          term: z.string(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const username = await sdk.getUsername(input);
        return {
          structuredContent: toolResult(
            'username',
            username.value,
            username.revealed,
          ),
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior3/5

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

The description adds minimal behavioral context beyond the annotations. Annotations indicate readOnlyHint=true, confirming it's a safe read operation, but the description doesn't disclose additional traits like rate limits, authentication needs, or what 'bw get username' implies (e.g., Bitwarden CLI reference). It doesn't contradict annotations, but offers little extra value.

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—a single sentence that directly states the tool's function without any fluff. It's front-loaded and wastes no words, making it efficient for quick understanding by an AI agent.

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

Completeness3/5

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

Given the tool's low complexity (one parameter, read-only per annotations) and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, parameter usage, or output, leaving gaps that could hinder correct tool invocation in more complex scenarios.

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 description mentions 'by search term', which aligns with the single parameter 'term' in the input schema. However, schema description coverage is 0%, so the schema provides no details on the parameter's meaning or format. The description adds some semantics but doesn't fully compensate, such as explaining what the search term targets or expected formats.

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 a login username') and resource ('by search term'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'keychain_get_item' or 'keychain_search_items', which might also retrieve usernames or related data, so it's not fully distinguished.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'keychain_get_item' for broader item retrieval or 'keychain_search_items' for more complex searches. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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