Skip to main content
Glama
Ming-321

mcp-feedback-enhanced

by Ming-321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_DEBUGNoDebug modefalse
MCP_LANGUAGENoForce UI language: zh-TW, zh-CN, or enAuto-detect
MCP_WEB_HOSTNoWeb UI host binding. Use 127.0.0.1 for local only or 0.0.0.0 for remote access.127.0.0.1
MCP_WEB_PORTNoWeb UI port (1024-65535)8765
MCP_DESKTOP_MODENoEnable desktop application mode (true/false)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
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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, 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. Only when the user explicitly indicates "end" or "no more interaction needed" can you stop calling this tool, and the process is considered complete.

  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_infoA

獲取系統環境資訊

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.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: one is for interactive feedback collection, the other for retrieving system information. There is no overlap or ambiguity.

Naming Consistency2/5

The tool names follow different conventions: 'feedback' is a simple noun, while 'get_system_info' uses a verb_noun pattern. This inconsistency could confuse an agent expecting a uniform naming scheme.

Tool Count2/5

With only 2 tools, the server feels under-scoped for its apparent purpose of feedback enhancement. The system info tool seems tangential, and the feedback tool alone does not justify a full server.

Completeness2/5

The server lacks essential tools for a feedback system, such as storing, retrieving, or analyzing past feedback. The presence of an unrelated system info tool further reduces coherence.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources