Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

delete_rule

Remove a specific rule from a feature flag in Flipt MCP Server by specifying the namespace, flag key, and rule ID to manage configurations effectively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flagKeyYes
namespaceKeyYes
ruleIdYes

Implementation Reference

  • The MCP tool handler function for 'delete_rule'. It executes the deletion via fliptClient and formats the MCP response.
    async args => {
      try {
        await fliptClient.deleteRule(args.namespaceKey, args.flagKey, args.ruleId);
    
        return {
          content: [
            {
              type: 'text',
              text: `Successfully deleted rule ${args.ruleId} from flag ${args.flagKey}`,
            },
          ],
        };
      } catch (error: any) {
        console.error('Error deleting rule:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Failed to delete rule: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema using Zod for validating namespaceKey, flagKey, and ruleId parameters.
    {
      namespaceKey: z.string().min(1),
      flagKey: z.string().min(1),
      ruleId: z.string().min(1),
    },
  • src/index.ts:965-997 (registration)
    Registers the 'delete_rule' tool with the MCP server, specifying name, input schema, and handler.
    server.tool(
      'delete_rule',
      {
        namespaceKey: z.string().min(1),
        flagKey: z.string().min(1),
        ruleId: z.string().min(1),
      },
      async args => {
        try {
          await fliptClient.deleteRule(args.namespaceKey, args.flagKey, args.ruleId);
    
          return {
            content: [
              {
                type: 'text',
                text: `Successfully deleted rule ${args.ruleId} from flag ${args.flagKey}`,
              },
            ],
          };
        } catch (error: any) {
          console.error('Error deleting rule:', error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to delete rule: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper method in FliptClient that calls the generated RulesServiceApi to delete the rule.
    async deleteRule(namespaceKey: string, flagKey: string, id: string) {
      try {
        await this.rulesApi.deleteRule(namespaceKey, flagKey, id);
        return { success: true };
      } catch (error) {
        console.error('Error deleting rule:', error);
        throw error;
      }
    }
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