Skip to main content
Glama
keywaysh

Keyway MCP Server

by keywaysh

keyway_list_environments

List available environments in your repository vault to manage secrets and configurations securely.

Instructions

List available environments for the current repository vault.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the `keyway_list_environments` tool, which retrieves the repository environments using helper functions.
    export async function listEnvironments(): Promise<CallToolResult> {
      const token = await getToken();
      const repository = getRepository();
    
      const environments = await getVaultEnvironments(repository, token);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({ repository, environments, count: environments.length }, null, 2),
          },
        ],
      };
    }
  • src/index.ts:68-73 (registration)
    The registration of the `keyway_list_environments` tool in the MCP server.
    server.tool(
      'keyway_list_environments',
      'List available environments for the current repository vault.',
      {},
      async () => listEnvironments()
    );
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 but does not cover traits like read-only vs. destructive nature, authentication needs, rate limits, or response format. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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 is front-loaded and appropriately sized for a simple tool with no parameters, making it highly concise and well-structured.

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, no annotations), the description is minimally adequate but lacks depth. It covers the basic purpose but does not address behavioral aspects or usage context, which could be beneficial for an AI agent to fully understand the tool's role and limitations.

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 no parameter information is needed. The description does not add any parameter details, which is appropriate given the schema's completeness, earning a baseline score of 4 for not introducing unnecessary or conflicting information.

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 the resource 'available environments for the current repository vault', making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'keyway_list_secrets', which might list a different type of resource, leaving room for slight ambiguity.

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, such as 'keyway_list_secrets' or other siblings. It lacks context on prerequisites, exclusions, or scenarios where this tool is preferred, offering only a basic statement of function without 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/keywaysh/keyway-mcp'

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