Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_secrets_delete

Remove a secret from Doppler to manage sensitive data securely. Specify the secret name, and optionally the project and config, to delete it from your workspace.

Instructions

Delete a secret from Doppler

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the secret to delete
projectNoThe Doppler project name (optional if set via doppler setup)
configNoThe Doppler config name (optional if set via doppler setup)

Implementation Reference

  • Specific case in buildDopplerCommand function that constructs the 'doppler secrets delete' CLI command for the doppler_secrets_delete tool.
    case "doppler_secrets_delete":
      parts.push("secrets", "delete", getString("name")!);
      if (getString("project")) parts.push("--project", getString("project")!);
      if (getString("config")) parts.push("--config", getString("config")!);
      parts.push("--json", "--yes"); // --yes to skip confirmation
      break;
  • Tool definition including name, description, and input schema for doppler_secrets_delete.
    {
      name: "doppler_secrets_delete",
      description: "Delete a secret from Doppler",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "The name of the secret to delete",
          },
          project: {
            type: "string",
            description: "The Doppler project name (optional if set via doppler setup)",
          },
          config: {
            type: "string",
            description: "The Doppler config name (optional if set via doppler setup)",
          },
        },
        required: ["name"],
      },
    },
  • src/index.ts:27-31 (registration)
    Registers the ListTools handler that returns the toolDefinitions array, making doppler_secrets_delete available.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: toolDefinitions,
      };
    });
  • MCP CallTool request handler that dispatches to executeCommand based on tool name, handling doppler_secrets_delete calls.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await executeCommand(name, args || {});
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        throw new McpError(ErrorCode.InternalError, `Doppler CLI error: ${errorMessage}`);
      }
    });
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 destructive action ('Delete') but doesn't cover critical aspects like whether deletion is permanent, requires specific permissions, has rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy or unnecessary elaboration.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address the tool's impact, error handling, or return values, leaving the agent with insufficient context for safe and effective use. More detail is needed for such a high-stakes operation.

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 all parameters documented in the schema. The description doesn't add any meaning beyond what the schema provides—it doesn't explain parameter interactions, default behaviors, or provide examples. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is added.

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 ('Delete') and resource ('a secret from Doppler'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'doppler_secrets_set' or 'doppler_secrets_get' beyond the obvious action difference, missing explicit scope or capability distinctions.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, when-not-to-use scenarios, or compare with siblings like 'doppler_secrets_set' for updates or 'doppler_secrets_list' for checking before deletion. The description lacks any contextual usage instructions.

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/aledlie/doppler-mcp'

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