Copilot Leecher
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| request_reviewA | 请求专家审查你完成的工作。调用此工具后，会话将被发送到审查服务器，你需要等待专家在 Web 界面上提供反馈。如果反馈是 "ok" 或 "approved"，表示工作已通过审查；否则，你需要根据反馈意见改进工作并再次请求审查。 |
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 'request_review' has a clear, distinct purpose that cannot be mistaken for any other functionality.
A single tool inherently exhibits perfect naming consistency as there are no other tools to compare against. The name 'request_review' follows a clear verb_noun pattern that would be consistent if more tools existed.
One tool is generally too few for most server purposes, as it severely limits functionality and scope. While the tool's purpose is clear, a single tool feels thin and incomplete for handling complex workflows, suggesting an extreme mismatch with typical server design.
The server appears to focus on review workflows, but with only one tool for requesting reviews, there are severe gaps. Missing are tools for submitting work, checking review status, handling feedback, or managing the review process, making the surface incomplete and likely to cause agent failures.