mcp-get-installed-apps
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-installed-appsB | Get my computer's installed apps |
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's purpose is clearly defined as retrieving installed apps from the computer, making it distinct by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'get-installed-apps' follows a clear verb-noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for most server purposes, as it limits functionality and suggests a thin or incomplete surface. While it might be appropriate for a very narrow scope, it generally feels insufficient for typical agent workflows.
The server's domain appears to be managing installed apps, but with only a 'get' operation, there are significant gaps. Missing operations like install, uninstall, update, or search apps make the surface incomplete and likely to cause agent failures for broader tasks.