Skip to main content
Glama
kukapay

crypto-whitepapers-mcp

search_whitepaper

Find and retrieve cryptocurrency whitepapers by searching DuckDuckGo. Input a project name to receive a JSON list of relevant PDFs, including titles, URLs, and snippets.

Instructions

Search for a cryptocurrency project's whitepaper PDF using DuckDuckGo.

Parameters:
    project_name (str): The name of the cryptocurrency project (e.g., 'bitcoin', 'ethereum').

Returns:
    str: A JSON-formatted list of search results with title, URL, and snippet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_nameYes

Implementation Reference

  • Registration of the 'search_whitepaper' tool using the @mcp.tool() decorator on the handler function.
    @mcp.tool()
  • The handler function that implements the logic for the 'search_whitepaper' tool. It performs a DuckDuckGo search for the project's whitepaper PDF and returns formatted JSON results.
    def search_whitepaper(project_name: str, ctx: Context = None) -> str:
        """Search for a cryptocurrency project's whitepaper PDF using DuckDuckGo.
    
        Parameters:
            project_name (str): The name of the cryptocurrency project (e.g., 'bitcoin', 'ethereum').
    
        Returns:
            str: A JSON-formatted list of search results with title, URL, and snippet.
        """
        try:
            with DDGS() as ddgs:
                query = f"{project_name} whitepaper filetype:pdf"
                results = ddgs.text(keywords=query, max_results=5)
            formatted_results = [
                {"title": r["title"], "url": r["href"], "snippet": r["body"]}
                for r in results
            ]
            return json.dumps(formatted_results, indent=2)
        except Exception as e:
            return f"Error searching for {project_name} whitepaper: {str(e)}"
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that it performs a web search via DuckDuckGo and returns JSON-formatted results, but does not mention behavioral traits such as rate limits, authentication needs, error handling, or whether it accesses external APIs. For a tool with no annotations, this leaves significant gaps in understanding its operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the core purpose, followed by clear sections for parameters and returns. Each sentence earns its place by providing essential information without redundancy, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (web search with one parameter) and no annotations or output schema, the description covers the basic purpose, parameters, and return format. However, it lacks details on behavioral aspects like error cases or search constraints, which could be important for an agent. It is adequate but has clear gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds substantial meaning beyond the input schema, which has 0% coverage. It explains that 'project_name' refers to 'the name of the cryptocurrency project' and provides examples ('bitcoin', 'ethereum'), clarifying the parameter's purpose and expected format. This fully compensates for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Search for a cryptocurrency project's whitepaper PDF') using a specific resource ('using DuckDuckGo'), which distinguishes it from sibling tools like 'load_whitepaper' (likely for loading content) and 'list_available_projects' (likely for listing projects). It provides a concrete verb+resource combination that is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by specifying the resource (cryptocurrency whitepapers) and search engine (DuckDuckGo), but does not explicitly state when to use this tool versus alternatives like 'ask_whitepapers' or 'load_whitepaper'. It provides context but lacks clear exclusions or named alternatives, leaving some ambiguity for the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kukapay/crypto-whitepapers-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server