Skip to main content
Glama
disnet
by disnet

list_vaults

Retrieve all configured vaults with their current status and details to manage your note-taking system.

Instructions

List all configured vaults with their status and information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_vaults tool logic, fetching vaults from globalConfig and formatting a markdown response.
    handleListVaults = async (): Promise<{
      content: Array<{ type: string; text: string }>;
    }> => {
      try {
        const vaults = this.globalConfig.listVaults();
    
        if (vaults.length === 0) {
          return {
            content: [
              {
                type: 'text',
                text: 'No vaults configured. Use create_vault to add your first vault.'
              }
            ]
          };
        }
    
        const vaultList = vaults
          .map(({ info, is_current }) => {
            const indicator = is_current ? '🟢 (current)' : '⚪';
            return `${indicator} **${info.id}**: ${info.name}\n   Path: ${info.path}\n   Created: ${new Date(info.created).toLocaleDateString()}\n   Last accessed: ${new Date(info.last_accessed).toLocaleDateString()}${info.description ? `\n   Description: ${info.description}` : ''}`;
          })
          .join('\n\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `📁 **Configured Vaults**\n\n${vaultList}`
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        return {
          content: [
            {
              type: 'text',
              text: `Failed to list vaults: ${errorMessage}`
            }
          ]
        };
      }
    };
  • The JSON schema definition for the list_vaults tool input (no parameters required).
    name: 'list_vaults',
    description: 'List all configured vaults',
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    }
  • Registration of the list_vaults tool in the CallToolRequestSchema switch statement, mapping the tool name to its handler method.
      return await this.vaultHandlers.handleListVaults();
    case 'create_vault':
  • src/server.ts:877-883 (registration)
    Tool metadata and schema registration in the ListToolsRequestSchema response.
    name: 'list_vaults',
    description: 'List all configured vaults with their status and information',
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    }
  • Helper method in GlobalConfigManager that retrieves the list of all vaults with current status, used by the handler.
    listVaults(): Array<{ info: VaultInfo; is_current: boolean }> {
      if (!this.#config) {
        return [];
      }
    
      return Object.entries(this.#config.vaults).map(([id, info]) => ({
        id,
        info,
        is_current: id === this.#config!.current_vault
      }));
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool lists vaults with status and information, which implies a read-only operation, but doesn't disclose behavioral traits such as permissions required, rate limits, pagination, or format of returned data. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 that front-loads the key action ('List all configured vaults') and adds necessary detail ('with their status and information'). There is no wasted verbiage, and every word contributes to understanding the tool's purpose.

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 has 0 parameters, no annotations, and no output schema, the description is minimally adequate. It specifies what the tool does but lacks details on return values, error handling, or operational context. For a simple list tool, it meets basic needs but could be more complete by describing the output structure or usage scenarios.

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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. Baseline for 0 parameters is 4, as it avoids unnecessary details.

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 verb ('List') and resource ('all configured vaults'), specifying what information is included ('status and information'). It distinguishes from sibling tools like 'get_current_vault' or 'create_vault' by indicating it returns all vaults rather than a single one or performing a mutation. However, it doesn't explicitly differentiate from potential similar tools like 'get_vaults' if they existed.

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 (e.g., needing configured vaults), exclusions, or comparisons to siblings like 'get_current_vault' for active vault or 'remove_vault' for deletion. Usage is implied by the action but not explicitly defined.

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/disnet/flint-note'

If you have feedback or need assistance with the MCP directory API, please join our Discord server