Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

list_segments

Retrieve all segments within a specified namespace to manage and evaluate feature flag targeting and user groupings effectively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceKeyYes

Implementation Reference

  • The MCP tool handler function for 'list_segments' that fetches segments via fliptClient.listSegments, formats the response as JSON text content with metadata URI, or returns an error response.
      try {
        const segments = await fliptClient.listSegments(args.namespaceKey);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(segments, null, 2),
            },
          ],
          _meta: {
            uri: `flipt://namespaces/${args.namespaceKey}/segments`,
          },
        };
      } catch (error: any) {
        console.error(`Error listing segments for namespace ${args.namespaceKey}:`, error);
        return {
          content: [
            {
              type: 'text',
              text: `Failed to list segments: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema for the 'list_segments' tool, requiring a non-empty namespaceKey string.
      namespaceKey: z.string().min(1),
    },
    async args => {
  • src/index.ts:423-454 (registration)
    Registration of the 'list_segments' MCP tool using server.tool, including name, schema, and handler.
      'list_segments',
      {
        namespaceKey: z.string().min(1),
      },
      async args => {
        try {
          const segments = await fliptClient.listSegments(args.namespaceKey);
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(segments, null, 2),
              },
            ],
            _meta: {
              uri: `flipt://namespaces/${args.namespaceKey}/segments`,
            },
          };
        } catch (error: any) {
          console.error(`Error listing segments for namespace ${args.namespaceKey}:`, error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to list segments: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper method in FliptClient class that invokes the generated SegmentsServiceApi.listSegments, extracts segments from response, and handles errors by returning empty array.
    async listSegments(namespaceKey: string) {
      try {
        const response = await this.segmentsApi.listSegments(namespaceKey);
        if (response && response.segments) {
          return response.segments;
        } else {
          console.error('Unexpected response structure:', response);
          return [];
        }
      } catch (error) {
        console.error(`Error getting segments for namespace ${namespaceKey}:`, error);
        return [];
      }
    }
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