Skip to main content
Glama

Send Template

keychain_send_template
Read-only

Generate JSON templates for Bitwarden Send objects to create secure file or text shares.

Instructions

Get json templates for send objects (bw send template).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectYes

Implementation Reference

  • The tool `keychain_send_template` is registered as `${deps.toolPrefix}.send_template` and calls `sdk.sendTemplate(input)` to execute its logic.
      `${deps.toolPrefix}.send_template`,
      {
        title: 'Send Template',
        description: 'Get json templates for send objects (bw send template).',
        annotations: { readOnlyHint: true, openWorldHint: true },
        inputSchema: {
          object: z.enum(['send.text', 'text', 'send.file', 'file']),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        const sdk = await deps.getSdk(extra.authInfo);
        const template = await sdk.sendTemplate(input);
        return {
          structuredContent: { template },
          content: [{ type: 'text', text: 'OK' }],
        };
      },
    );
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation that may return incomplete data. The description adds that this tool retrieves 'json templates,' which suggests it returns structured data formats rather than actual send objects. This clarifies the tool's behavior beyond the annotations, though it doesn't detail response format, error conditions, or rate limits.

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 a single sentence that is technically concise, but it's under-specified rather than efficiently informative. It wastes no words but fails to provide necessary context. The structure is straightforward but lacks front-loading of critical information.

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 the tool's apparent purpose (retrieving templates for send operations), the description is incomplete. It doesn't explain what 'send' means in this context, how the templates are used, or what the output looks like (no output schema is provided). With annotations covering safety but not behavioral details, and schema coverage at 0%, the description should do more to compensate.

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?

The input schema has 1 parameter with 0% description coverage (no schema descriptions). The description mentions 'send objects' which loosely relates to the 'object' parameter's enum values ('send.text', 'text', 'send.file', 'file'), but it doesn't explain what these values mean, their differences, or how they affect the output. The description adds minimal semantic context beyond the bare schema.

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

Purpose2/5

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

The description 'Get json templates for send objects (bw send template)' restates the tool name 'Send Template' and title 'Send Template' without adding meaningful specificity. It mentions 'json templates' and 'send objects' but doesn't clearly explain what a 'send object' is or what the templates are used for. The phrase 'bw send template' appears to be jargon without explanation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 any of the sibling tools (like keychain_send_create, keychain_send_get, keychain_send_list) that appear related to 'send' operations, nor does it explain how this template retrieval fits into the workflow. No prerequisites, constraints, or use cases are indicated.

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