Feedback Collector MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| collect_feedbackB | Collect feedback from the user through an Electron app |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'collect_feedback' has a clearly distinct purpose that cannot be mistaken for any other tool in this server.
The single tool name 'collect_feedback' follows a clear verb_noun pattern. With only one tool, there is no inconsistency in naming conventions to evaluate, making it perfectly consistent.
A single tool is too few for most server purposes, as it limits functionality and suggests a thin or incomplete implementation. While it might be appropriate for a very narrow scope, it generally feels insufficient for robust agent interaction.
The server appears to be for collecting feedback, but with only a collection tool, there are severe gaps: no tools for viewing, analyzing, updating, or managing feedback. This makes the surface severely incomplete for any meaningful feedback management workflow.