crypto-whitepapers-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 |
|---|---|
| search_whitepaperA | Search for a cryptocurrency project's whitepaper PDF using DuckDuckGo. |
| load_whitepaperA | Load a whitepaper PDF from a URL into the knowledge base. |
| ask_whitepapersA | Search the knowledge base for information related to a query, optionally filtered by project. |
| list_available_projectsA | List all cryptocurrency projects available in the knowledge base. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_tokenomics | Analyze the tokenomics described in a cryptocurrency whitepaper |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have overlapping purposes that could cause confusion. 'ask_whitepapers' and 'search_whitepaper' both involve searching, but one queries the knowledge base while the other searches the web via DuckDuckGo. 'load_whitepaper' and 'list_available_projects' are more distinct, but the two search tools have unclear boundaries that might lead to misselection.
The naming follows a consistent verb_noun pattern throughout, such as 'ask_whitepapers', 'list_available_projects', 'load_whitepaper', and 'search_whitepaper'. There is a minor deviation with 'ask_whitepapers' using plural 'whitepapers' while others use singular 'whitepaper', but overall the pattern is predictable and readable.
With 4 tools, the count is reasonable for a server focused on managing cryptocurrency whitepapers. It covers key operations like searching, listing, loading, and web searching. It might be slightly thin, but each tool earns its place without feeling excessive or insufficient for the domain.
The tool set covers basic operations but has notable gaps. It allows loading and searching whitepapers, but lacks update or delete functionality for managing the knowledge base. There is no tool to view or retrieve a specific loaded whitepaper's content directly, which could limit agent workflows for in-depth analysis.