Agent Feedback Loop
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| report_tool_resultA | Report the result of using an MCP tool. Helps build a quality database so agents can discover which tools work best for which tasks. Args: tool_name: Name of the tool used (e.g. "get_weather") success: Whether the tool call was successful quality_score: Quality rating 1-10 (10 = perfect) task_description: What you were trying to do server_name: Which MCP server the tool belongs to response_time_ms: How long the call took in milliseconds error_message: Error message if the call failed |
| get_tool_qualityA | Get quality metrics for a specific MCP tool. Shows success rate, average quality score, and recent feedback. Args: tool_name: Name of the tool to check |
| get_best_toolsB | Get the highest-rated MCP tools, optionally filtered by task type. Shows the best tools based on community feedback data. Args: task: Filter by task description keyword (optional) limit: Max results (default: 10) |
| get_trending_toolsB | Get trending MCP tools based on recent usage and feedback. Shows which tools are being used most and rated highest recently. Args: days: Look back period in days (default: 7) limit: Max results (default: 10) |
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 4 tools
Each tool has a clearly distinct purpose: get_best_tools retrieves top-rated tools, get_tool_quality provides metrics for a specific tool, get_trending_tools shows recent trends, and report_tool_result submits feedback. There is no overlap in functionality, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern with underscores (e.g., get_best_tools, get_tool_quality, get_trending_tools, report_tool_result). The naming is predictable and readable throughout the set.
With 4 tools, the count is reasonable for a feedback loop server, covering core operations like querying and reporting. It might feel slightly thin if advanced features like analytics or bulk operations are needed, but it's well-scoped for basic functionality.
The tool set covers key aspects of a feedback system: retrieving best tools, checking specific tool quality, viewing trends, and submitting reports. A minor gap is the lack of tools for managing or aggregating feedback data, but agents can work around this with the provided operations.