books-word-converter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONVERTER_SERVER_URL | Yes | URL of the AI Studio converter server used for PDF-to-Word/Markdown conversion. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_books_directoryB | Scans a local directory for PDF and Word books, calculates total file count, estimated pages, and file sizes. |
| convert_book_to_wordA | Converts a single PDF or document into a professional Word (.docx) and Markdown (.md) file with strict RTL Arabic layout fidelity. |
| batch_convert_folderB | Executes a sequential, low-memory batch conversion on an entire folder (e.g. 150+ books). Automatically bundles every N books into a timestamped ZIP archive and maintains resume state. |
| get_batch_statusA | Checks the current batch progress and resume state of a conversion directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: scanning for inventory, converting one book, batch converting a folder, and checking batch status. The boundary between single and batch conversion is explicit, and status checking is separate from execution.
All names use snake_case and begin with recognizable action-oriented terms. The pattern is mostly verb_object, though convert_book_to_word and batch_convert_folder add extra descriptive segments that slightly break a strict convention.
Four tools is well-scoped for a book conversion server. Each tool earns its place by covering discovery, single conversion, batch conversion, and progress tracking without redundancy.
The surface covers the main lifecycle: scanning inputs, converting a single file, batch converting folders with resume state, and checking batch progress. Minor gaps exist around cancellation, output listing, or conversion option configuration, but core workflows are supported.