Skip to main content
Glama
kelleyblackmore

Vault MCP Server

vault_list

Lists secrets stored at a specified path in HashiCorp Vault to view available secret data.

Instructions

List secrets at the specified path in Vault

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesThe path to list secrets from (e.g., 'secret/metadata')

Implementation Reference

  • Handler logic for the 'vault_list' tool within the CallToolRequestSchema handler. It extracts the 'path' argument, calls vaultClient.list(path), and returns the result data as a JSON-formatted text content block.
    case "vault_list": {
      const { path } = args as { path: string };
      const result = await vaultClient.list(path);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:63-76 (registration)
    Registration of the 'vault_list' tool in the TOOLS array, which is returned by ListToolsRequestHandler. Includes name, description, and inputSchema.
    {
      name: "vault_list",
      description: "List secrets at the specified path in Vault",
      inputSchema: {
        type: "object",
        properties: {
          path: {
            type: "string",
            description: "The path to list secrets from (e.g., 'secret/metadata')",
          },
        },
        required: ["path"],
      },
    },
  • Input schema for the 'vault_list' tool, defining a required 'path' string property.
    inputSchema: {
      type: "object",
      properties: {
        path: {
          type: "string",
          description: "The path to list secrets from (e.g., 'secret/metadata')",
        },
      },
      required: ["path"],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose whether this is a read-only operation (implied but not stated), what permissions are required, whether it returns metadata or just names, pagination behavior, error conditions, or rate limits. For a Vault operation with zero annotation coverage, this leaves significant behavioral gaps.

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 wasted words. It's front-loaded with the core action ('List secrets') and includes essential context ('at the specified path in Vault'). Every element earns its place.

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?

For a Vault secrets listing tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the listing returns (keys, metadata, recursive listing), whether it requires specific authentication, or how it handles empty paths or permissions errors. The agent lacks crucial operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with the path parameter fully documented in the schema. The description adds minimal value beyond the schema by reinforcing that the path is 'specified' and mentioning Vault context. This meets the baseline 3 for high schema coverage where the schema does the heavy lifting.

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 ('secrets at the specified path in Vault'), making the purpose immediately understandable. It distinguishes from siblings like vault_read (which reads secret values) and vault_write/vault_delete (which modify data). However, it doesn't explicitly mention that this lists secret names/keys rather than values, which would make it a perfect 5.

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 context through 'at the specified path' and the sibling tools provide natural alternatives, but there's no explicit guidance about when to use this versus vault_read or how it differs from vault_read (which retrieves secret values). The agent must infer usage patterns from tool names alone.

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/kelleyblackmore/vault-mcp'

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