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`, `timeout`, plus `conversation_id`, which a Cursor hook fills in: never set it yourself. 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. Queued messages: While you work between two calls, the user can keep typing in the Web UI; those messages are queued (at most 3) and reach you in one of two ways, both under a header starting with `（你工作期间，用户追加了 N 条消息`: - After any tool call, a Cursor hook appends the queue to that tool's result. Images are saved as local files whose paths are listed in the block: open them with ``Read``. - On your next call to this tool, the queue is returned immediately, without waiting for a new reply. Either way they are NOT an answer to the ``summary`` you just passed: treat them as new instructions in the given order, act on them, then call this tool again. Args: project_directory: Absolute or relative project path. Defaults to cwd. summary: Required Markdown summary. No empty string, no placeholder. timeout: Seconds to wait for user feedback. Values above `600` are capped, so always pass `600`. conversation_id: Filled in by a Cursor hook. Never set it yourself. 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. A result starting with `[interactive_feedback TIMEOUT]` means the user has not replied within the wait limit — re-call to keep waiting.
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, timeout, plus conversation_id, which a Cursor hook fills in: never set it yourself. 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.

Queued messages: While you work between two calls, the user can keep typing in the Web UI; those messages are queued (at most 3) and reach you in one of two ways, both under a header starting with （你工作期间，用户追加了 N 条消息:

- After any tool call, a Cursor hook appends the queue to that
  tool's result. Images are saved as local files whose paths are
  listed in the block: open them with ``Read``.
- On your next call to this tool, the queue is returned
  immediately, without waiting for a new reply.

Either way they are NOT an answer to the ``summary`` you just
passed: treat them as new instructions in the given order, act on
them, then call this tool again.

Args: project_directory: Absolute or relative project path. Defaults to cwd. summary: Required Markdown summary. No empty string, no placeholder. timeout: Seconds to wait for user feedback. Values above 600 are capped, so always pass 600. conversation_id: Filled in by a Cursor hook. Never set it yourself.

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. A result starting with [interactive_feedback TIMEOUT] means the user has not replied within the wait limit — re-call to keep waiting.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.8/5.0

Scored 2026-10-23 20:20 across 2 tools

Disambiguation4/5

The two tools have clearly different runtime behaviors: interactive_feedback drives user dialogue, while get_system_info reads environment data. There is no direct overlap, but get_system_info appears unrelated to the feedback domain, which weakens the overall set coherence.

Naming Consistency3/5

Both names use snake_case, so they are readable and mechanically consistent. However, interactive_feedback is a noun/adjective phrase while get_system_info follows a verb_noun pattern, so the naming convention is mixed rather than predictable.

Tool Count3/5

Two tools is borderline thin for a server whose core purpose is interactive feedback, especially when one tool carries almost all the domain behavior. The second tool is a small unrelated utility rather than a complementary feedback operation.

Completeness3/5

interactive_feedback is richly specified and covers many runtime states such as timeout, queued messages, images, and termination handling. However, there are no explicit session-management or history tools, and get_system_info is isolated from the feedback workflow.

Maintenance

ActivityMaintained

ResponsivenessNo issues