crypto-trending-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 |
|---|---|
| get_trending_md_docA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| parse_trending_md_doc | Guide the MCP client to parse the trending coins table from a CoinGecko Markdown document using an LLM. Args: doc (str): The Markdown document containing the trending coins table. Returns: A string with instructions for the LLM to extract and parse the table. |
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 between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare against. The name 'get_trending_md_doc' follows a clear verb_noun pattern.
One tool is too few for a server named 'crypto-trending-mcp', which suggests a broader scope for cryptocurrency trending data. A single tool limits functionality and makes the server feel incomplete or trivial for its apparent purpose.
The server is severely incomplete for a cryptocurrency trending domain. It only retrieves a Markdown document from CoinGecko, lacking tools for filtering, sorting, analyzing trends, or accessing other trending sources, which are essential for comprehensive coverage.