Skip to main content
Glama

Send Get

keychain_send_get
Read-only

Retrieve secure file or text sends from your Bitwarden vault using their unique ID, with options to download files or view text content.

Instructions

Get Sends owned by you. Use text=true to return text content; downloadFile=true to download a file send (bw send get).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
textNo
downloadFileNo

Implementation Reference

  • Registration and tool handler for 'keychain_send_get'. Note the typo in the user prompt: the actual tool name is 'send_get' (with the prefix).
      `${deps.toolPrefix}.send_get`,
      {
        title: 'Send Get',
        description:
          'Get Sends owned by you. Use text=true to return text content; downloadFile=true to download a file send (bw send get).',
        annotations: { readOnlyHint: true, openWorldHint: true },
        inputSchema: {
          id: z.string(),
          text: z.boolean().optional(),
          downloadFile: z.boolean().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const result = await sdk.sendGet(input);
        return {
          structuredContent: { result },
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
  • Actual implementation of 'sendGet' logic within the Keychain SDK.
    async sendGet(input: {
      id: string;
      text?: boolean;
      downloadFile?: boolean;
    }): Promise<unknown> {
      return this.bw.withSession(async (session) => {
        if (input.text) {
          const { stdout } = await this.bw.runForSession(
            session,
            ['--raw', 'send', 'get', input.id, '--text'],
            { timeoutMs: 60_000 },
          );
          return { text: stdout.trim() };
        }
    
        if (input.downloadFile) {
          const dir = await mkdtemp(join(tmpdir(), 'keychain-sendfile-'));
          try {
            await this.bw.runForSession(
              session,
              ['send', 'get', input.id, '--output', dir],
              { timeoutMs: 120_000 },
            );
            const file = await this.readSingleFileAsBase64(dir);
            return { file };
          } finally {
            await rm(dir, { recursive: true, force: true });
          }
        }
    
        const { stdout } = await this.bw.runForSession(
          session,
          ['send', 'get', input.id],
          {
            timeoutMs: 60_000,
          },
        );
        return this.tryParseJson(stdout);
      });
    }
Behavior4/5

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

Annotations indicate read-only and open-world behavior, which the description aligns with by describing a retrieval operation. The description adds valuable context about ownership ('owned by you') and the effects of optional parameters (returning text content or downloading files), which aren't covered by annotations.

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 front-loaded with the core purpose, followed by concise parameter guidance. Both sentences earn their place by adding distinct value—no wasted words or redundancy.

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?

For a retrieval tool with read-only annotations and no output schema, the description covers ownership and parameter effects adequately. However, it lacks details on response format, error conditions, or pagination, which would be helpful given the complexity of handling sends with optional content types.

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?

With 0% schema description coverage, the description compensates well by explaining the purpose of two optional parameters ('text' and 'downloadFile'). It doesn't cover the required 'id' parameter's semantics, but the added value for the optional parameters is significant given the schema gap.

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 Sends') and specifies ownership scope ('owned by you'), which distinguishes it from potentially public or shared sends. However, it doesn't explicitly differentiate from sibling tools like 'keychain_send_list' or 'keychain_get_item', which might also retrieve send-related data.

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 implies usage for retrieving sends with optional text or file content, but lacks explicit guidance on when to use this versus alternatives like 'keychain_send_list' (for listing) or 'keychain_get_item' (for general item retrieval). It mentions parameter usage but not tool selection context.

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