common_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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_basic_detailsC | Returns basic system and runtime details. |
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. The single tool has a clear and distinct purpose.
There is only one tool, so naming consistency is not an issue. The name 'get_basic_details' follows a clear verb_noun pattern.
Having only one tool feels thin for a server labeled 'common_mcp'. While a single tool can be appropriate for very narrow scopes, this server's name suggests a broader utility, making the count borderline.
The server only provides basic system and runtime details. For a 'common' server, one would expect additional tools for other common operations, leaving significant gaps.