Skip to main content
Glama
Dwsy

mcp-feedback-enhanced

by Dwsy

interactive_feedback

Gather user feedback during AI workflows to adjust actions and confirm next steps. Supports quick selection options and conversation tracking for iterative task completion.

Instructions

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.

CONVERSATION_ID USAGE:

  • IMPORTANT: Always provide a consistent conversation_id for the same chat window or conversation thread

  • If your IDE or client provides a conversation/thread/chat ID, use it as the conversation_id

  • Using the same conversation_id will replace the previous feedback session for that conversation

  • This allows multiple AI conversations to have independent feedback sessions without interfering with each other

  • Examples:

    • Cursor: Use the conversation UUID from the chat window

    • VS Code: Use the conversation/thread identifier

    • If no ID is available: Generate a UUID once per conversation and reuse it

  • If conversation_id is not provided, a new one will be auto-generated (may cause session conflicts in multi-conversation scenarios)

QUICK OPTIONS FEATURE: You can provide quick selection options in the summary using XML format. Users can click checkboxes to select options.

Basic Format:

Format with Attributes (optional title, key, description):

Multiple option groups are supported:

User selections will be returned in the feedback with group numbers like "[1] A. First option".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNoAI 工作完成的摘要說明我已完成了您請求的任務。
timeoutNo等待用戶回饋的超時時間(秒)
conversation_idNo會話唯一標識符,用於區分不同的對話窗口。為同一個對話使用一致的 ID 以保持會話連續性。如果未提供,將自動生成新 ID。
project_directoryNo專案目錄路徑.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully bears the transparency burden. It discloses that reusing a conversation_id replaces prior sessions, auto-generated IDs may conflict, and user selections are returned with group numbers. It also details the quick-options feature and timeout behavior implied by the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but well-organized into clear sections (USAGE RULES, CONVERSATION_ID USAGE, QUICK OPTIONS FEATURE). Every paragraph adds necessary operational detail, though the repeated emphasis on calling the tool could be condensed. Minor redundancy prevents a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's interactive nature and the presence of an output schema, the description covers all critical aspects: when to call, how to manage conversation IDs, how to present options, and what happens to selections. It is complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters, but the description adds substantial meaning beyond field names. It explains conversation_id handling with examples (Cursor, VS Code), how summary can embed clickable options, and the role of project_directory in user feedback. This enriches the schema's terse descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Interactive feedback collection tool for LLM agents,' clearly specifying the verb (collect) and resource (feedback). The usage rules elaborate on when to invoke it, distinguishing it from the sibling tool get_system_info which is unrelated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The USAGE RULES section provides explicit when-to-use guidance: call during any process, repeatedly unless termination, and stop only on explicit user indication. It also explains how to handle feedback and summarize actions, leaving no ambiguity about alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dwsy/mcp-feedback-enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server