geeknews-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 |
|---|---|
| get_articlesA | |
| get_weekly_newsB | |
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 2 tools
The two tools have clearly distinct purposes: get_articles retrieves articles by type (top, new, ask, show) with a limit parameter, while get_weekly_news fetches weekly news by ID or the most recent one. There is no overlap in functionality or ambiguity between them.
Both tools follow a consistent verb_noun naming pattern (get_articles and get_weekly_news), using snake_case throughout. The naming is predictable and readable without any deviations or mixed conventions.
With only 2 tools, the server feels thin and under-scoped for a news domain. While the tools cover basic retrieval, there are likely missing operations (e.g., searching, filtering, or interacting with articles) that would enhance functionality, making the count too low for comprehensive coverage.
The tool surface is severely incomplete for a news server. It only provides read operations (get_articles and get_weekly_news) with no support for creating, updating, deleting, or searching articles. This lack of CRUD/lifecycle coverage will limit agent capabilities and cause failures in more complex workflows.