EndNote Library Reader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENL_FILE | Yes | Path to the EndNote .enl file (required) | |
| ENABLE_LOG | No | Enable detailed log output (optional) | |
| USE_BACKUP | No | Use .enl.backup for all DB operations (optional, enables backup mode) | |
| DATA_FOLDER | Yes | Path to the EndNote .Data folder (required) |
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 |
|---|---|
No tools | |
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
There is some overlap between list_papers and search_papers, as both return lists of papers with similar metadata, which could cause confusion about when to use each. However, read_paper and refresh_backup have distinct purposes, and the descriptions help clarify that search_papers is for fuzzy title/keyword searches while list_papers is for paginated listing.
All tool names follow a consistent verb_noun pattern with snake_case, such as list_papers, read_paper, refresh_backup, and search_papers. This makes the tool set predictable and easy to understand.
With 4 tools, the count is reasonable for a library reader focused on paper retrieval and management. It covers core operations like listing, searching, reading, and backup refresh, though it might be slightly thin if more advanced features like updating or deleting papers were expected.
The tool set covers basic read operations (list, search, read) and a utility (refresh_backup), but lacks CRUD completeness for a paper management system, as there are no tools for creating, updating, or deleting papers. This could lead to gaps in agent workflows that require full lifecycle management.