Skip to main content
Glama
squirrelogic

Feature-Discussion MCP Server

by squirrelogic

begin_feature_discussion

Start a new feature discussion to explore implementation options, architecture considerations, and best practices with AI guidance.

Instructions

Start a new feature discussion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle or name of the feature

Implementation Reference

  • The switch case handler that executes the 'begin_feature_discussion' tool. It generates a feature ID, initializes the feature discussion object with the provided title and sets the first prompt, creates discussion context, and returns a response with the feature ID and initial prompt.
    case "begin_feature_discussion": {
      const { title } = request.params.arguments as any;
      const id = `f${Object.keys(featureDiscussions).length + 1}`;
    
      // Initialize new feature discussion
      featureDiscussions[id] = {
        id,
        title,
        description: "",
        requirements: [],
        status: 'in-discussion',
        createdAt: new Date().toISOString(),
        updatedAt: new Date().toISOString(),
        currentPrompt: FEATURE_DISCUSSION_PROMPTS[0].id
      };
    
      // Initialize discussion context
      discussionContexts[id] = {
        previousDecisions: [],
        relatedFeatures: [],
        technicalConstraints: [],
        conversationHistory: []
      };
    
      // Return the first prompt
      return {
        content: [
          {
            type: "text",
            text: `Feature discussion started for: ${title}\n\nFeature ID: ${id}\n\nFirst question:\n${FEATURE_DISCUSSION_PROMPTS[0].message}`
          }
        ]
      };
    }
  • src/index.ts:175-188 (registration)
    Registers the 'begin_feature_discussion' tool by defining its name, description, and input schema (requiring a 'title' string) in the ListToolsRequestSchema handler.
    {
      name: "begin_feature_discussion",
      description: "Start a new feature discussion",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "Title or name of the feature"
          }
        },
        required: ["title"]
      }
    },
  • Defines the array of sequential prompts used throughout feature discussions. The 'begin_feature_discussion' tool initializes new discussions with the first prompt from this array ('initial_description').
    const FEATURE_DISCUSSION_PROMPTS: FeaturePrompt[] = [
      {
        id: "initial_description",
        message: "Please provide a brief description of the feature you'd like to discuss.",
        field: "description"
      },
      {
        id: "business_value",
        message: "What business value does this feature provide? How does it benefit users or stakeholders?",
        field: "businessValue"
      },
      {
        id: "target_users",
        message: "Who are the target users for this feature?",
        field: "targetUsers"
      },
      {
        id: "requirements",
        message: "What are the key requirements or constraints for this feature?",
        field: "requirements"
      },
      {
        id: "success_criteria",
        message: "What are the success criteria for this feature? How will we know it's working as intended?",
        field: "successCriteria"
      },
      {
        id: "technical_approach",
        message: "Do you have any specific technical approach in mind for implementing this feature?",
        field: "technicalApproach"
      },
      {
        id: "risks",
        message: "Are there any potential risks or challenges we should consider?",
        field: "risks"
      },
      {
        id: "timeline",
        message: "What's the desired timeline or priority for this feature?",
        field: "timeline"
      }
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Start a new feature discussion' implies a creation/mutation operation, but it doesn't specify permissions needed, whether this is reversible, what happens after starting, or any rate limits. It lacks crucial context for safe and effective use.

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 with zero wasted words. It's appropriately sized for a simple tool and front-loads the core purpose immediately.

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

Completeness2/5

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

Given no annotations, no output schema, and a mutation tool with behavioral gaps, the description is incomplete. It doesn't explain what 'starting a feature discussion' entails, what the result looks like, or how it relates to the sibling tool. More context is needed for effective use.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents the single 'title' parameter. The description adds no additional meaning about parameters beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Start a new feature discussion' clearly indicates the action (start) and resource (feature discussion), but it's somewhat vague about what this entails. It doesn't specify what a 'feature discussion' is in this context or how it differs from the sibling tool 'provide_feature_input'.

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 the sibling 'provide_feature_input'. There's no mention of prerequisites, context, or alternatives. The user must infer usage from the tool 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/squirrelogic/mcp-feature-discussion'

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