LibraLM MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIBRALM_API_KEY | Yes | Your LibraLM API key (get one at libralm.com) |
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 |
|---|---|
| list_booksB | List all available books with their basic information |
| get_book_summaryB | Get the main summary for a book |
| get_book_detailsB | Get detailed information about a specific book |
| get_table_of_contentsB | Get the table of contents for a book with chapter descriptions |
| get_chapter_summaryC | Get the summary for a specific chapter of a book |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_book | Generate a prompt to analyze a book's themes and content |
| compare_books | Generate a prompt to compare two books |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Every tool has a clearly distinct purpose with no ambiguity. 'get_book_details' provides comprehensive information, 'get_book_summary' focuses on the main summary, 'get_chapter_summary' targets specific chapters, 'get_table_of_contents' offers structural overview, and 'list_books' enumerates available books. The descriptions make it easy to distinguish between these related but non-overlapping functions.
All tools follow a consistent verb_noun pattern using snake_case throughout. The naming convention is perfectly uniform with 'get_' or 'list_' prefixes followed by specific resource identifiers, making the tool set highly predictable and readable for agents.
Five tools is well-scoped for a book/library management server, with each tool earning its place. This count provides comprehensive coverage for book exploration without being overwhelming or insufficient, falling within the ideal 3-15 tool range for focused domain coverage.
The tool surface provides excellent read-only coverage for book exploration, including listing, detailed views, summaries, and structural information. The only minor gap is the absence of write operations (create/update/delete books or chapters), but for a library/reading-focused server, this is reasonable and agents can work effectively with the provided retrieval tools.