bookmeter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOKS_JSON | No | Path to the books.json file (default: books.json in the server directory) |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_mediaA | タイトル・作者のキーワードでメディア記録(本・映画・アニメ・ゲーム)を検索する（「これ読んだ/観た/やった?」判定用）。type未指定なら全種別を横断検索 |
| media_by_creatorB | 指定した作者(著者・監督・開発元など)のメディア記録を全件返す。type未指定なら全種別を対象にする |
| media_statsC | メディア記録の総件数・種別内訳・感想を書いた数・作者別トップN・年別件数を集計する。type指定でその種別のみ集計 |
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 3 tools
Each tool has a clearly distinct purpose: retrieving records by creator, aggregating statistics, and searching by keyword. No overlap.
All names follow a consistent verb_noun snake_case pattern: media_by_creator, media_stats, search_media.
3 tools is on the lower end but acceptable for a query-focused server. However, it feels slightly thin for a media tracking service.
Missing essential tools for adding, updating, or deleting media records, and no tool to retrieve a single record by ID. The surface is read-only, which is a significant gap.