Schema | gl-mcp-feedback

gl-mcp-feedback

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MCP_DEBUG`	No	调试模式，值为true/false	false
`MCP_LANGUAGE`	No	强制指定界面语言，支持 zh-TW, zh-CN, en	自动检测
`MCP_WEB_HOST`	No	Web UI 主机绑定，IP地址或主机名	127.0.0.1
`MCP_WEB_PORT`	No	Web UI 端口，1024-65535	8765

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

Capability	Details
`tools`	{ "listChanged": true }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`extensions`	{ "io.modelcontextprotocol/ui": {} }
`experimental`	{}

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
interactive_feedbackA	Open a Web UI to collect interactive feedback from the user. This tool is the PRIMARY communication channel with the user. The full list of "when to call" scenarios lives in the project's gl-mcp-feedback user rules; this docstring only covers the runtime contract that the tool itself enforces. Strict prohibitions: - While this tool is available, DO NOT invoke Cursor's built-in `AskQuestion`. Route every question through `summary` as a numbered list. - DO NOT end the turn with a plain-text reply when there is substantive content for the user to read. Put it in `summary`. - When the user skips without feedback, re-call this tool to ask why; only stop on explicit termination (`结束` / `不用了` / `stop` / `done`). - Allowed parameters: `project_directory`, `summary`, `title`, `timeout`. Names like `question` / `choices` / `options` belong to `AskQuestion` and will fail schema validation here. `summary` writing rules: - Markdown: headings (##), lists, tables, code fences, bold for key decisions. Include modified file paths and explicit questions when applicable. - NEVER pass an empty string or the placeholder phrase `我已完成了您请求的任务。` — runtime validation rejects them and you must re-call with a real summary. `title` writing rules: - Optional, ≤30 chars headline shown in the browser tab and summary header. Leave empty when `summary` is self-explanatory. - Examples: `需要你提供更多信息` / `修复完成，请验证` / `实现方案确认`. Args: project_directory: Absolute or relative project path. Defaults to cwd. summary: Required Markdown summary. No empty string, no placeholder. title: Optional short headline for the Web UI tab and summary header. timeout: Seconds to wait for user feedback. Keep `>= 600`. Returns: ToolResult: TextContent with the user's text feedback plus MCPImage objects for any uploaded images. An empty result means the user skipped — re-call to ask why.
get_system_infoA	获取系统环境信息 Returns: str: JSON 格式的系统信息

interactive_feedbackA

Open a Web UI to collect interactive feedback from the user.

This tool is the PRIMARY communication channel with the user. The full list of "when to call" scenarios lives in the project's gl-mcp-feedback user rules; this docstring only covers the runtime contract that the tool itself enforces.

Strict prohibitions: - While this tool is available, DO NOT invoke Cursor's built-in AskQuestion. Route every question through summary as a numbered list. - DO NOT end the turn with a plain-text reply when there is substantive content for the user to read. Put it in summary. - When the user skips without feedback, re-call this tool to ask why; only stop on explicit termination (结束 / 不用了 / stop / done). - Allowed parameters: project_directory, summary, title, timeout. Names like question / choices / options belong to AskQuestion and will fail schema validation here.

summary writing rules: - Markdown: headings (##), lists, tables, code fences, bold for key decisions. Include modified file paths and explicit questions when applicable. - NEVER pass an empty string or the placeholder phrase 我已完成了您请求的任务。 — runtime validation rejects them and you must re-call with a real summary.

title writing rules: - Optional, ≤30 chars headline shown in the browser tab and summary header. Leave empty when summary is self-explanatory. - Examples: 需要你提供更多信息 / 修复完成，请验证 / 实现方案确认.

Args: project_directory: Absolute or relative project path. Defaults to cwd. summary: Required Markdown summary. No empty string, no placeholder. title: Optional short headline for the Web UI tab and summary header. timeout: Seconds to wait for user feedback. Keep >= 600.

Returns: ToolResult: TextContent with the user's text feedback plus MCPImage objects for any uploaded images. An empty result means the user skipped — re-call to ask why.

get_system_infoA

获取系统环境信息

Returns: str: JSON 格式的系统信息

Prompts

Interactive templates invoked by user choice

Name	Description
`chat`	通过 Web UI 与用户开始互动反馈对话。使用此 prompt 快速启动反馈交流。 AI 会调用 interactive_feedback 工具打开 Web UI，通过浏览器界面与用户进行互动。

Resources

Contextual data attached and managed by the client

Name	Description
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

A4/5.0

Scored 2026-08-13 22:20 across 2 tools

Disambiguation5/5

Each tool serves a clearly distinct purpose: interactive_feedback collects user feedback via a web UI, and get_system_info retrieves system environment details. There is no overlap or ambiguity between them.

Naming Consistency2/5

The tool names do not follow a consistent pattern. 'interactive_feedback' is an adjective-noun phrase while 'get_system_info' follows a verb_noun convention, mixing styles and making the set feel inconsistent.

Tool Count3/5

With only 2 tools, the server is on the thin side. The system info tool seems unrelated to the core feedback domain, so the count feels slightly inflated for the apparent purpose.

Completeness4/5

The interactive_feedback tool provides a complete feedback loop, including handling skips, termination, and rich summaries, so there are no obvious gaps in the primary purpose. The system info tool is an extra that doesn't address any feedback-related gap.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers