Skip to main content
Glama
kelleyblackmore

Vault MCP Server

vault_read

Retrieve secrets from HashiCorp Vault by specifying the secret path to access stored sensitive data securely.

Instructions

Read a secret from Vault at the specified path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesThe path to read the secret from (e.g., 'secret/data/myapp')

Implementation Reference

  • The handler for the vault_read tool. It extracts the path from arguments, reads the secret using vaultClient.read(path), and returns the result data as formatted JSON text content.
    case "vault_read": {
      const { path } = args as { path: string };
      const result = await vaultClient.read(path);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:31-44 (registration)
    Registration of the vault_read tool in the TOOLS array, including its name, description, and input schema definition for the 'path' parameter.
    {
      name: "vault_read",
      description: "Read a secret from Vault at the specified path",
      inputSchema: {
        type: "object",
        properties: {
          path: {
            type: "string",
            description: "The path to read the secret from (e.g., 'secret/data/myapp')",
          },
        },
        required: ["path"],
      },
    },
  • Input schema definition for the vault_read tool, specifying the required 'path' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        path: {
          type: "string",
          description: "The path to read the secret from (e.g., 'secret/data/myapp')",
        },
      },
      required: ["path"],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool reads a secret, implying a read-only operation, but doesn't clarify critical aspects like authentication requirements, rate limits, error conditions (e.g., if the path doesn't exist), or what the output looks like (e.g., secret data format). This is a significant gap for a tool interacting with a secure system like Vault.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('Read a secret'), making it easy to parse. Every part of the sentence contributes to understanding, with no wasted verbiage.

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 complexity of interacting with Vault (a secure secret management system), the description is incomplete. There are no annotations to cover behavioral traits, no output schema to explain return values, and the description lacks details on authentication, error handling, or output format. For a tool with security implications, this leaves too many gaps for reliable agent use.

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?

The input schema has 100% description coverage, with the 'path' parameter well-documented in the schema itself (including an example). The description adds minimal value by mentioning 'the specified path' but doesn't provide additional context beyond what the schema already covers, such as path format constraints or Vault-specific nuances. Baseline 3 is appropriate given the high schema coverage.

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 ('Read') and resource ('a secret from Vault'), making the purpose immediately understandable. It specifies the target ('at the specified path'), which helps distinguish it from other operations like listing or writing. However, it doesn't explicitly differentiate from sibling tools like vault_list (which might list paths rather than read secrets).

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 like vault_list or vault_write. It mentions the path parameter but doesn't explain prerequisites (e.g., authentication needs) or scenarios where reading is appropriate over other operations. This leaves the agent without context for tool selection among siblings.

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