Skip to main content
Glama
Sign In
mcp-feedback-enhanced

mcp-feedback-enhanced

by Minidoracat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_DEBUGNoDebug mode toggle. Set to 'true' to enable debug output.false
MCP_LANGUAGENoForce UI language. Options: 'zh-TW', 'zh-CN', 'en'. Leave unset for auto-detection.auto-detect
MCP_WEB_HOSTNoWeb UI host binding. Use '0.0.0.0' for remote access.127.0.0.1
MCP_WEB_PORTNoWeb UI port number (1024-65535).8765
MCP_DESKTOP_MODENoEnable desktop application mode. Set to 'true' to use native desktop app.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
interactive_feedbackA

Interactive feedback collection tool for LLM agents.

USAGE RULES:

  1. During any process, task, or conversation, whether asking, replying, or completing phased tasks, you must call this tool to ask for feedback.

  2. Unless receiving termination instructions, or this tool returns a "no user response" result, all steps must repeatedly call this tool.

  3. Whenever user feedback is received, if the feedback content is not empty, you must call this tool again and adjust behavior based on the feedback content.

  4. You can stop calling this tool, and the process is considered complete, when the user explicitly indicates "end" or "no more interaction needed", or when this tool returns a "no user response" result (the wait timed out or the user closed the feedback UI) — in that case finish the task and do NOT call this tool again.

  5. You should summarize what have done, and provide project directory through args to let user know what you have done to provide feedback for next step.

get_system_infoC

獲取系統環境資訊

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: interactive_feedback collects user feedback, while get_system_info retrieves environment information. There is no meaningful overlap or risk of misselection.

Naming Consistency4/5

Both names use snake_case, which is consistent. However, interactive_feedback is a noun phrase rather than a verb_noun pattern like get_system_info, creating a minor stylistic deviation.

Tool Count3/5

Two tools is thin for a dedicated server, even one focused on feedback collection. The system-info tool is only loosely related to the core feedback purpose, making the set feel under-scoped.

Completeness3/5

The primary feedback collection operation is present, but there are no companion operations for session management, feedback history, or explicit completion/cancellation. The system-info tool adds unrelated functionality rather than filling lifecycle gaps.

Maintenance

ActivityNo data
ResponsivenessSyncing

Resources