Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Send List

keychain_send_list
Read-only

Retrieve a list of secure file and text shares from your password vault. Use this tool to view all Bitwarden Send items you own.

Instructions

List all the Sends owned by you (bw send list).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/registerTools.ts:886-902 (handler)
    Registration and handler implementation for keychain_send_list (registered as .send_list).
      `${deps.toolPrefix}.send_list`,
  {
    title: 'Send List',
    description: 'List all the Sends owned by you (bw send list).',
    annotations: { readOnlyHint: true, openWorldHint: true },
    inputSchema: {},
    _meta: toolMeta,
  },
  async (_input, extra) => {
    const sdk = await deps.getSdk(extra.authInfo);
    const sends = await sdk.sendList();
    return {
      structuredContent: { sends },
      content: [{ type: 'text', text: 'OK' }],
    };
  },
);

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating a safe read operation with potentially large results. The description adds context by specifying 'owned by you,' which clarifies scope beyond annotations. It doesn't detail behavioral traits like pagination or rate limits, but with annotations covering safety, this adds moderate 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 a single, efficient sentence with zero waste. It front-loads the core action ('List all the Sends') and includes essential scope ('owned by you'), making it appropriately sized and well-structured.

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

Completeness4/5

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

Given 0 parameters, annotations covering safety, and no output schema, the description is mostly complete. It specifies scope ('owned by you'), but lacks details on output format or potential limitations like pagination. For a simple list tool, this is sufficient but not exhaustive.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate. Baseline is 4 for 0 parameters, as it doesn't need to compensate for any gaps.

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

Purpose5/5

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

The description clearly states the verb ('List') and resource ('all the Sends owned by you'), specifying the scope as owned items. It distinguishes from siblings like keychain_send_get (retrieves a specific Send) and keychain_send_create (creates a Send), making the purpose specific and differentiated.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by stating 'owned by you,' which suggests it's for viewing personal Sends. However, it doesn't explicitly mention when not to use it or name alternatives like keychain_search_items for broader searches, so it provides clear context but lacks exclusions or named alternatives.

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