Skip to main content
Glama

Get Exposed

keychain_get_exposed
Read-only

Check if passwords or credentials have been exposed in data breaches by searching with a specific term to identify security risks.

Instructions

Check exposed status by search term (bw get exposed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes

Implementation Reference

  • Implementation of the 'get_exposed' tool, which checks Bitwarden vault item exposure status.
      `${deps.toolPrefix}.get_exposed`,
      {
        title: 'Get Exposed',
        description: 'Check exposed status by search term (bw get exposed).',
        annotations: { readOnlyHint: true },
        inputSchema: {
          term: z.string(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const exposed = await sdk.getExposed(input);
        return {
          structuredContent: toolResult(
            'exposed',
            exposed.value,
            exposed.revealed,
          ),
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds minimal behavioral context with 'by search term', suggesting a lookup based on input, but doesn't disclose details like rate limits, authentication needs, or what 'exposed' entails. It doesn't contradict annotations, so no penalty, but adds little beyond them.

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

Conciseness4/5

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

The description is a single, efficient sentence with zero waste, front-loaded with the core action. However, it's slightly under-specified, as more detail could improve clarity without losing conciseness.

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?

Given no output schema and low schema coverage (0%), the description lacks completeness. It doesn't explain return values (e.g., what 'exposed status' includes), error conditions, or behavioral nuances. For a tool with one parameter and no annotations beyond readOnlyHint, it should provide more context to guide effective use.

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?

Schema description coverage is 0%, so the schema provides no param details. The description mentions 'by search term', which hints at the 'term' parameter's purpose, but doesn't explain what the term should be (e.g., username, password, item name) or its format. It adds some meaning but insufficiently compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Check exposed status by search term' states a clear verb ('Check') and resource ('exposed status'), but it's vague about what 'exposed status' refers to (e.g., passwords, credentials, data breaches) and doesn't distinguish from siblings like 'keychain_search_items' or 'keychain_get_item'. It avoids tautology by not just restating the name/title.

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. It doesn't mention prerequisites, exclusions, or compare to sibling tools like 'keychain_search_items' for broader searches. Usage is implied only by the action 'check exposed status', but no explicit context is given.

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