Skip to main content
Glama
orime

mcp-feedback-enhanced-community-fix

by orime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_DEBUGNo是否输出调试日志false
MCP_LANGUAGENo界面语言自动检测
MCP_WEB_HOSTNoWeb UI 监听地址127.0.0.1
MCP_WEB_PORTNoWeb UI 端口8765
MCP_DESKTOP_MODENo是否启用桌面模式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

獲取系統環境資訊

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

Scored across 2 tools

Disambiguation5/5

The two tools serve entirely distinct purposes: one retrieves system information, the other collects feedback. There is no overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern using snake_case ('get_system_info' and 'interactive_feedback'), making them predictable.

Tool Count3/5

With only two tools, the server feels minimal. However, for a focused feedback-collection purpose with a system info utility, the count is acceptable, though many servers would offer more.

Completeness4/5

The server covers its stated domain (feedback collection and system info) adequately. The feedback tool is designed for repeated use mid-task, so no additional CRUD tools are needed. Minor gap: no way to retrieve past feedback, but rules imply continuous interaction.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources