Compresto 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 |
|---|---|
| get-total-usersB | Get total users of Compresto |
| get-total-processed-filesB | Get total processed files of Compresto |
| get-total-size-reducedC | Get total file size reduced of Compresto |
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 3 tools
Each tool has a clearly distinct purpose: one retrieves processed file count, another gets size reduction data, and the third provides user count. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern with hyphens (e.g., get-total-processed-files, get-total-size-reduced, get-total-users). This uniformity enhances readability and predictability across the tool set.
With only 3 tools, the set feels thin for a server named 'Compresto MCP', which might imply broader functionality. However, the tools are well-scoped for reporting metrics, so it's borderline but not severely lacking.
The tools only provide read-only metrics (get operations) with no ability to perform actions like processing files, managing users, or configuring settings. This creates significant gaps for a server that might be expected to handle file processing or user management tasks.