Skip to main content
Glama
ispyridis

Calibre RAG MCP Server

by ispyridis

list_projects

Retrieve all available RAG projects for organizing and searching your Calibre ebook library content.

Instructions

List all available RAG projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:1004-1011 (registration)
    Registration of the list_projects tool including its name, description, and empty input schema in the tools/list response.
        name: 'list_projects',
        description: 'List all available RAG projects',
        inputSchema: {
            type: 'object',
            properties: {},
            required: []
        }
    },
  • Handler implementation in handleToolsCall switch case. Lists projects from this.projects Map, computes stats, formats a markdown text response and structured projects array.
    case 'list_projects':
        const projectList = Array.from(this.projects.entries()).map(([name, config]) => ({
            name,
            description: config.description,
            book_count: config.books.length,
            chunk_count: config.chunk_count,
            created_at: config.created_at,
            last_updated: config.last_updated
        }));
        
        this.sendSuccess(id, {
            content: [{
                type: 'text',
                text: `Available RAG Projects (${projectList.length}):\n\n` +
                    projectList.map(p => 
                        `• **${p.name}**: ${p.description}\n` +
                        `  Books: ${p.book_count}, Chunks: ${p.chunk_count}\n` +
                        `  Created: ${p.created_at}\n`
                    ).join('\n')
            }],
            projects: projectList
        });
        break;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List all available' implies a read-only operation, it doesn't specify important behavioral aspects like whether results are paginated, sorted, or limited in scope. The description lacks details about permissions, rate limits, or what 'available' means in this 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 a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple listing tool and gets straight to the point.

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?

For a zero-parameter listing tool without annotations or output schema, the description provides the minimum viable information about what the tool does. However, it lacks important context about the return format, scope limitations, or how this differs from similar sibling tools, leaving gaps in understanding when and how to use it effectively.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't waste space discussing parameters that don't exist, earning a baseline score of 4 for this dimension.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('RAG projects'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools like 'search' or 'get_project_info', which might also retrieve project information in different ways.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'search', 'get_project_info', or 'search_project_context'. It doesn't specify whether this returns all projects without filtering, or if there are specific contexts where this tool is preferred over others.

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

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/ispyridis/calibre-rag-mcp-nodejs'

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