MCP Server Demo
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 |
|---|---|
| fetch_news_articlesB | |
| addC | Add two numbers |
| get_weatherC | it gets and retuns the weather of the 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 purpose with no overlap: 'add' performs arithmetic, 'fetch_news_articles' retrieves news data, and 'get_weather' provides weather information. The descriptions reinforce these unique domains, making misselection unlikely.
The naming is inconsistent with mixed conventions: 'add' uses a simple verb, 'fetch_news_articles' follows a verb_noun pattern with snake_case, and 'get_weather' uses a verb_noun pattern but with different verb style ('get' vs 'fetch'). This lack of pattern reduces predictability.
With only 3 tools, the server feels thin and under-scoped for a general-purpose 'MCP Server Demo', as it covers unrelated domains (math, news, weather) without depth in any area. This minimal set suggests a lack of coherent focus.
The tool set is severely incomplete for any discernible domain; it appears to be a random collection of unrelated utilities. There are obvious gaps, such as no update or delete operations for news or weather, and no coverage of basic workflows beyond simple fetches and addition.