Skip to main content
Glama
nullmastermind

mcp-feedback-enhanced-gw

by nullmastermind
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_DEBUGNoDebug mode (true/false)false
MCP_LANGUAGENoForce UI language (zh-TW/zh-CN/en)Auto-detect
MCP_WEB_HOSTNoWeb UI host binding127.0.0.1
MCP_WEB_PORTNoWeb UI port8765
MCP_DESKTOP_MODENoDesktop 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
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, 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

Get system environment information

Returns: str: System information in JSON format

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 have completely unrelated purposes: one handles interactive feedback collection, the other retrieves system information. There is no overlap or confusion between them.

Naming Consistency4/5

Both names use snake_case, but 'interactive_feedback' uses an adjective+noun pattern while 'get_system_info' follows verb+noun. This minor inconsistency prevents a perfect score.

Tool Count2/5

With only two tools, the server feels underdeveloped. The name suggests a feedback-focused gateway, yet only one tool is feedback-related and the other is unrelated system info.

Completeness2/5

The feedback tool is described extensively but there is no explicit end tool, retrieval of prior feedback, or integration with the system info tool. The overall domain coverage is sparse and ad hoc.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources