Skip to main content
Glama
duolabmeng6

Interactive Feedback MCP

by duolabmeng6

interactive_feedback

Request interactive feedback on project changes by providing a directory path and summary, enabling collaborative review and improvement suggestions.

Instructions

Request interactive feedback for a given project directory and summary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_directoryYesFull path to the project directory
summaryYesShort, one-line summary of the changes

Implementation Reference

  • The core handler function for the 'interactive_feedback' tool. Registered via @mcp.tool() decorator. Input schema defined via Annotated with Field descriptions. Launches UI subprocess and processes result.
    @mcp.tool()
    def interactive_feedback(
        project_directory: Annotated[str, Field(description="Full path to the project directory")],
        summary: Annotated[str, Field(description="Short, one-line summary of the changes")],
    ) -> Dict[str, str]:
        """Request interactive feedback for a given project directory and summary"""
        
        result_dict = launch_feedback_ui(first_line(project_directory), first_line(summary))
        return header_data(result_dict)
  • Helper function that launches the feedback_ui.py subprocess, passing project_directory and summary, captures JSON output.
    def launch_feedback_ui(project_directory: str, summary: str) -> dict[str, str]:
        # Create a temporary file for the feedback result
        with tempfile.NamedTemporaryFile(suffix=".json", delete=False) as tmp:
            output_file = tmp.name
    
        try:
            # Get the path to feedback_ui.py relative to this script
            script_dir = os.path.dirname(os.path.abspath(__file__))
            feedback_ui_path = os.path.join(script_dir, "feedback_ui.py")
    
            # Run feedback_ui.py as a separate process
            args = [
                sys.executable,
                "-u",
                feedback_ui_path,
                "--project-directory", project_directory,
                "--prompt", summary,
                "--output-file", output_file
            ]
            result = subprocess.run(
                args,
                check=False,
                shell=False,
                stdout=subprocess.DEVNULL,
                stderr=subprocess.DEVNULL,
                stdin=subprocess.DEVNULL,
                close_fds=True
            )
            if result.returncode != 0:
                raise Exception(f"Failed to launch feedback UI: {result.returncode}")
    
            # Read the result from the temporary file
            with open(output_file, 'r') as f:
                result = json.load(f)
            os.unlink(output_file)
            return result
        except Exception as e:
            if os.path.exists(output_file):
                os.unlink(output_file)
            raise e
  • Helper function that processes the result from UI: extracts logs, feedback text, compresses and converts uploaded images to MCP Image objects, returns as tuple.
    def header_data(result_dict: dict) -> tuple:
        # print(result_dict)
        # {'logs': '', 'interactive_feedback': 'asdasdas', 'uploaded_images': ['/Users/ll/Desktop/2025/interactive-feedback-mcp/images/feedback.png']}
    
        logs = result_dict.get("logs", "")
        interactive_feedbacktxt = result_dict.get("interactive_feedback", "")
        uploaded_images = result_dict.get("uploaded_images", [])
    
        processed_content: List[Union[str, Image]] = []
    
        if logs and logs != "":
            processed_content.append("收集的日志: \n" + logs)
        
        if interactive_feedbacktxt and interactive_feedbacktxt != "":
            processed_content.append("用户反馈信息: \n" + interactive_feedbacktxt)
        
        for image_path in uploaded_images:
            image_data,img_format = compress_image(image_path)
            mcp_image = Image(data=image_data, format=img_format)
            processed_content.append(mcp_image)
            
        return tuple(processed_content)
  • Helper for compressing images if >800KB, thumbnails if needed, returns image data and format.
    def compress_image(image_path: str):
        pil_img = PILImage.open(image_path)
        img_format = (pil_img.format or "PNG").lower()
        temp_image_path = image_path + ".temp.jpg"
        if os.path.getsize(image_path) > 800 * 1024:
            img_format = (pil_img.format or "jpg").lower()
    
            pil_img.save(temp_image_path, optimize=True, quality=50)
            # 输出现在的尺寸
            # print(f"压缩前大小: {friendly_size(os.path.getsize(image_path))}")
            # print(f"压缩后大小: {friendly_size(os.path.getsize(temp_image_path))}")
            if os.path.getsize(temp_image_path) > 800 * 1024:
                pil_img.thumbnail((512, 512))
                pil_img.save(temp_image_path, optimize=True, quality=50)
                # print(f"缩放后大小: {friendly_size(os.path.getsize(temp_image_path))}")
                # print(f"缩放后大小: {friendly_size(os.path.getsize(temp_image_path))}")
            with open(temp_image_path, "rb") as f:
                image_data = f.read()
            os.unlink(temp_image_path)
            return image_data,img_format
        else:
            with open(image_path, "rb") as f:
                image_data = f.read()
            return image_data, img_format
  • FastMCP server instance creation, required for tool registration via decorators.
    mcp = FastMCP("Interactive Feedback MCP", log_level="ERROR")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to explain what 'interactive feedback' entails—whether it blocks, returns data, requires user input, or has side effects. This is insufficient for an agent to understand the tool's behavior.

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

Conciseness4/5

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

The description is a single, clear sentence with no extraneous information. While concise, it could benefit from additional structure or brevity, but it effectively communicates the core purpose without waste.

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?

The tool has a simple parameter set (2 strings) and no output schema, but the description omits critical context: what does 'interactive feedback' mean? Is feedback returned or is it a blocking interaction? The minimalism leaves an agent guessing about the tool's complete behavior.

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?

The input schema covers 100% of parameters with descriptions. The tool description merely restates 'project directory and summary', adding no extra meaning. Schema coverage is high, so baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb 'Request', the resource 'interactive feedback', and the context 'for a given project directory and summary'. It is specific and unambiguous, leaving no doubt about the tool's core function.

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

Usage Guidelines3/5

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

The description implies usage by stating 'Request interactive feedback' but provides no explicit guidance on when to use this tool or any alternatives. Since there are no sibling tools, differentiation is not needed, but the description lacks contextual cues for optimal use.

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