Skip to main content
Glama

bookshelf_config

Retrieve or update Bookshelf settings by selecting an operation and passing arguments, covering development, download clients, hosts, indexers, UI, and naming.

Instructions

bookshelf config operations on Bookshelf. Pass operation and an arguments dict matching that operation's parameters.

  • bookshelf_get_config_development() — List config development.

  • bookshelf_get_config_development_by_id(id) — Fetch a single config development by id.

  • bookshelf_get_config_downloadclient() — List config downloadclient.

  • bookshelf_get_config_downloadclient_by_id(id) — Fetch a single config downloadclient by id.

  • bookshelf_get_config_host() — List config host.

  • bookshelf_get_config_host_by_id(id) — Fetch a single config host by id.

  • bookshelf_get_config_indexer() — List config indexer.

  • bookshelf_get_config_indexer_by_id(id) — Fetch a single config indexer by id.

  • bookshelf_get_config_mediamanagement() — List config mediamanagement.

  • bookshelf_get_config_mediamanagement_by_id(id) — Fetch a single config mediamanagement by id.

  • bookshelf_get_config_metadataprovider() — List config metadataprovider.

  • bookshelf_get_config_metadataprovider_by_id(id) — Fetch a single config metadataprovider by id.

  • bookshelf_get_config_naming() — List config naming.

  • bookshelf_get_config_naming_by_id(id) — Fetch a single config naming by id.

  • bookshelf_get_config_naming_examples(rename_books=None, replace_illegal_characters=None, colon_replacement_format=None, standard_book_format=None, author_folder_format=None, include_author_name=None, include_book_title=None, include_quality=None, replace_spaces=None, separator=None, number_style=None, id=None, resource_name=None) — List config naming examples. Query params: renameBooks, replaceIllegalCharacters, colonReplacementFormat, standardBookFormat, authorFolderFormat, includeAuthorName, includeBookTitle, includeQuality, replaceSpaces, separator, numberStyle, id, resourceName.

  • bookshelf_get_config_ui() — List config ui.

  • bookshelf_get_config_ui_by_id(id) — Fetch a single config ui by id.

  • bookshelf_get_localization() — List localization.

  • bookshelf_list_update() — List update.

  • bookshelf_update_config_development(id, body={}) — Update config development. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_config_downloadclient(id, body={}) — Update config downloadclient. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_config_host(id, body={}) — Update config host. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_config_indexer(id, body={}) — Update config indexer. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_config_mediamanagement(id, body={}) — Update config mediamanagement. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_config_metadataprovider(id, body={}) — Update config metadataprovider. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_config_naming(id, body={}) — Update config naming. WRITE: this modifies your Bookshelf instance.

  • bookshelf_update_config_ui(id, body={}) — Update config ui. WRITE: this modifies your Bookshelf instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

D1.8/5.0
Behavior2/5

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

For update operations, the description explicitly notes 'WRITE: this modifies your Bookshelf instance,' which is useful. However, it does not disclose any other behavioral traits such as read-only guarantees, side effects, error handling, or potential performance implications. Without annotations, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a long, repetitive list of operations without an introductory summary or clear structure. It front-loads no context and each line follows the same pattern, making it verbose and harder to scan. A more concise summary with grouped operations would be more effective.

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

Completeness2/5

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

Given the large number of operations (27), the description lacks essential context: no examples, no explanation of what each config resource represents, no mention of common use cases, and no information about return structures. The output schema is not referenced, and the description does not compensate for the complexity.

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

Parameters2/5

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

The schema defines only 'operation' and 'arguments' (a generic object), and the description adds minimal parameter meaning. Operation names reveal some expected arguments (e.g., 'id' for *_by_id and 'body' for update), but the structure and content of the 'arguments' object are not explained, leaving parameter semantics largely ambiguous.

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

Purpose2/5

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

The description labels the tool as 'bookshelf config operations' but provides no high-level purpose or explanation of what this configuration manages. Each operation's one-liner (e.g., 'List config development') gives a narrow sense of individual actions, but the overall tool's role remains vague and does not clearly differentiate it from sibling tools.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives like bookshelf_media_library or bookshelf_indexers. It lacks any indication of typical scenarios, prerequisites, or context where these config operations would be preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/arr-mcps/bookshelf-mcp'

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