Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

delete_namespace

Remove a namespace from the Flipt MCP Server to manage feature flags and segments efficiently by specifying the unique key associated with it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes

Implementation Reference

  • Primary handler and registration for the 'delete_namespace' MCP tool. Validates input with Zod schema, executes deletion via fliptClient, and returns appropriate MCP response.
    server.tool(
      'delete_namespace',
      {
        key: z.string().min(1),
      },
      async args => {
        try {
          await fliptClient.deleteNamespace(args.key);
          return {
            content: [
              {
                type: 'text',
                text: `Deleted namespace ${args.key}`,
              },
            ],
          };
        } catch (error: any) {
          console.error('Error deleting namespace:', error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to delete namespace: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Input schema definition using Zod for the tool's 'key' parameter.
    {
      key: z.string().min(1),
    },
  • FliptClient helper method implementing the namespace deletion by calling the generated NamespacesServiceApi.
    async deleteNamespace(key: string) {
      try {
        await this.namespacesApi.deleteNamespace(key);
        return { success: true };
      } catch (error) {
        console.error('Error deleting namespace:', error);
        throw error;
      }
    }
  • Alternative or supporting handler method in ToolHandlers class (potentially unused).
    async handleDeleteNamespace({ key }: { key: string }) {
      try {
        await this.fliptClient.deleteNamespace(key);
        return {
          content: [
            {
              type: 'text',
              text: `Successfully deleted namespace: ${key}`,
            },
          ],
        };
      } catch (error) {
        console.error(`Error deleting namespace ${key}:`, error);
        return {
          content: [
            {
              type: 'text',
              text: `Error deleting namespace ${key}: ${error}`,
            },
          ],
          isError: true,
        };
      }
  • Generated API method for deleting namespace in NamespacesServiceApi.
    public async deleteNamespace(key: string, force?: boolean, _options?: Configuration): Promise<RequestContext> {
        let _config = _options || this.configuration;
    
        // verify required parameter 'key' is not null or undefined
        if (key === null || key === undefined) {
            throw new RequiredError("NamespacesServiceApi", "deleteNamespace", "key");
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Related 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/flipt-io/mcp-server-flipt'

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