crypto-projects-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_project_dataC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| format_project_data | Format cryptocurrency project data into a Markdown document. Args: token_symbol (str): The symbol of the cryptocurrency token to fetch and format lang (str, optional): Language for formatting (e.g., 'en_US', 'zh_CN'). Defaults to None, using system locale. Returns: list[UserMessage]: Messages containing formatted Markdown content |
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.
The single tool name follows a clear verb_noun pattern (get_project_data), and with no other tools to compare, consistency is inherently perfect.
One tool is too few for a server named 'crypto-projects-mcp', which suggests a broader scope. This minimal set severely limits functionality, as it only supports fetching data without any create, update, delete, or search operations.
The tool surface is severely incomplete for the implied domain of cryptocurrency projects. It lacks essential operations like listing projects, searching, updating, or deleting data, making it inadequate for typical agent workflows in this domain.