coindesk-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 |
|---|---|
| read_newsA | |
| recent_newsA | |
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: read_news extracts full content from a specific article URL, while recent_news fetches a list of recent articles from an RSS feed. There is no overlap in functionality, and an agent can easily distinguish between retrieving a single article versus getting multiple recent articles.
Both tools follow a consistent verb_noun pattern (read_news and recent_news) with clear, descriptive names. The naming convention is uniform throughout the tool set, making it predictable and easy for agents to understand.
With only 2 tools, the server feels thin for a news domain. While the tools cover reading specific articles and listing recent ones, there are likely gaps such as searching news, filtering by category, or accessing historical archives. The count is too low for comprehensive news interaction.
The tool surface is significantly incomplete for a news server. It lacks essential operations like searching for articles by keyword, filtering by date or category, and accessing older or archived news. Agents will struggle with basic news-related tasks beyond the two provided functions.