User Feedback
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 |
|---|---|
| user_feedbackC | Request user feedback for a given project directory and summary |
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 ambiguity or overlap between tools. The tool 'user_feedback' has a singular, clear purpose, so an agent cannot misselect among alternatives.
The single tool name 'user_feedback' follows a consistent snake_case pattern. Since there is only one tool, there is no inconsistency in naming conventions to evaluate.
A single tool is too few for most server purposes, as it limits functionality and suggests a thin or incomplete surface. For a server named 'User Feedback', one tool may not adequately cover potential operations like viewing, managing, or analyzing feedback.
The tool set is severely incomplete for a 'User Feedback' domain. It only provides a way to request feedback, missing essential operations such as retrieving, updating, deleting, or listing feedback, which are necessary for a full CRUD lifecycle.