Skip to main content
Glama
kukapay

crypto-whitepapers-mcp

by kukapay
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_available_projects

Retrieve a JSON-formatted list of cryptocurrency project names from the crypto-whitepapers-mcp knowledge base for analysis or reference.

Instructions

List all cryptocurrency projects available in the knowledge base.

Parameters:
    None

Returns:
    str: A JSON-formatted list of project names derived from PDF filenames.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/crypto_whitepapers_mcp/cli.py:116-134 (handler)
    The handler function for the 'list_available_projects' tool. It scans the WHITEPAPERS_DIR for PDF files and returns a JSON list of project names derived from the filenames.
    @mcp.tool()
def list_available_projects(ctx: Context) -> str:
    """List all cryptocurrency projects available in the knowledge base.

    Parameters:
        None

    Returns:
        str: A JSON-formatted list of project names derived from PDF filenames.
    """
    try:
        projects = [
            os.path.splitext(f)[0]
            for f in os.listdir(WHITEPAPERS_DIR)
            if f.endswith(".pdf")
        ]
        return json.dumps(projects, indent=2)
    except Exception as e:
        return f"Error listing projects: {str(e)}"
  • src/crypto_whitepapers_mcp/cli.py:116-116 (registration)
    The @mcp.tool() decorator registers the list_available_projects function as an MCP tool.
    @mcp.tool()

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists projects and returns JSON, but lacks details on rate limits, authentication needs, data freshness, or error handling. It adequately describes the core behavior but misses operational context.

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 front-loaded with the core purpose, followed by structured sections for parameters and returns. Every sentence adds value without redundancy, making it efficient and easy to parse for an AI agent.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is mostly complete. It explains the action, source, and return format. However, it could enhance completeness by mentioning data derivation from PDF filenames more prominently or noting any limitations.

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

Parameters4/5

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

The description explicitly notes 'Parameters: None,' which adds clarity beyond the empty input schema. With 0 parameters and 100% schema coverage, the baseline is 4, as the description confirms no inputs are required, compensating for any potential ambiguity.

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 ('List all cryptocurrency projects') and resource ('available in the knowledge base'), distinguishing it from sibling tools that focus on whitepaper operations rather than project listing. It precisely communicates what the tool does without ambiguity.

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

Usage Guidelines4/5

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

The description implies usage context by specifying 'available in the knowledge base,' which helps differentiate from other data sources. However, it lacks explicit guidance on when to use this tool versus alternatives like 'search_whitepaper' for filtering, or prerequisites for accessing the knowledge base.

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