whoami-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 |
|---|---|
| whoamiB | Returns the username of the current system user as my identity. |
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, making disambiguation perfect. The tool 'whoami' has a single, clear purpose that cannot be mistaken for any other function.
Since there is only one tool, naming consistency is inherently perfect as there are no other tools to compare against. The tool name 'whoami' is clear and follows a common Unix command pattern, which is appropriate for its purpose.
A single tool is generally too few for most server purposes, as it limits functionality and can feel thin or incomplete. While it might be appropriate for a minimal utility, it lacks the breadth typically expected in an MCP server, which often requires multiple tools for varied operations.
The tool 'whoami' covers its specific function of returning the current system user's identity, but with only one tool, the server's scope is very narrow. There are no obvious gaps for this limited purpose, but it lacks broader coverage that might be expected in a user management or system information domain.