Skip to main content
Glama
aledlie

Doppler MCP Server

by aledlie

doppler_projects_list

Retrieve a list of all projects in your Doppler workspace to manage secrets and configurations across applications.

Instructions

List all Doppler projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Switch case within buildDopplerCommand that constructs the Doppler CLI command 'doppler projects list --json' to execute the tool logic for listing Doppler projects.
    case "doppler_projects_list":
      parts.push("projects", "list");
      parts.push("--json");
      break;
  • Tool schema definition for doppler_projects_list, including name, description, and empty input schema (no parameters required).
    {
      name: "doppler_projects_list",
      description: "List all Doppler projects",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:27-31 (registration)
    Registration of tool list handler that exposes the doppler_projects_list tool via the toolDefinitions array in MCP ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: toolDefinitions,
      };
    });
  • MCP CallTool request handler that dispatches to executeCommand based on tool name, handling the execution and response formatting for doppler_projects_list.
    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 action ('List') but doesn't describe how the listing works (e.g., pagination, ordering, rate limits, or authentication needs). For a list operation with zero annotation coverage, this is a significant gap in transparency.

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 any wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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's simplicity (0 parameters, no output schema), the description is adequate as a basic list operation. However, with no annotations and no output schema, it lacks details on behavioral aspects like response format or limitations, which could be helpful for an agent. It meets minimum viability but has clear gaps.

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 the schema fully documents the absence of parameters. The description doesn't need to add parameter information, and it correctly implies no inputs are required for listing all projects. A baseline of 4 is appropriate for zero-parameter tools.

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 Doppler projects'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'doppler_configs_list' or 'doppler_environments_list' beyond specifying the resource type, which prevents a perfect score.

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 'doppler_configs_list' or 'doppler_environments_list'. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on the resource name 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/aledlie/doppler-mcp'

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