my-mcp-server
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 |
|---|---|
| greetC | Greet someone with a personalized message |
| calculateC | Perform basic math calculations |
| weather_infoB | Get weather information for a city |
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 and non-overlapping purpose: calculate handles math, greet handles messaging, and weather_info handles weather data. An agent can easily tell them apart with no risk of misselection.
The naming is mixed: calculate and greet are verbs, while weather_info is a noun phrase. There is no consistent verb_noun pattern, but the names are still readable and descriptive.
With only 3 tools, the server feels thin and under-scoped for a general-purpose MCP server. The tools cover unrelated domains (math, greeting, weather), suggesting a lack of cohesive focus.
The server lacks a clear domain, making completeness hard to assess. Each tool stands alone without supporting operations (e.g., no update or delete for weather), leading to significant gaps in any potential workflow.