Skip to main content
Glama
Minidoracat

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": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

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_infoB

獲取系統環境資訊

Returns: str: JSON 格式的系統資訊

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are completely distinct: interactive_feedback is for user interaction, while get_system_info retrieves system information. There is no overlap in purpose.

Naming Consistency4/5

Both use snake_case, but one is a noun phrase (interactive_feedback) and the other is a verb phrase (get_system_info), showing minor inconsistency in naming convention.

Tool Count3/5

With only two tools, the server is very thin; while both are useful, it feels under-scoped for a feedback-enhanced purpose and could benefit from additional related utilities.

Completeness3/5

The interactive feedback tool covers a feedback loop but lacks a dedicated tool to submit feedback or query feedback history. get_system_info is unrelated to the core feedback domain, suggesting incomplete integration.

Maintenance

ActivityNo data
ResponsivenessSlow

Resources