Library MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_by_tagC | Get blog content by its tag. Args: tag: the tag associated with content limit: the number of results to include |
| get_by_textC | Get blog content by text in content. Args: query: text for an exact match limit: the number of results to include |
| rebuildA | Rebuild text index. Useful for when contents have changed on disk |
| search_tagsB | Search for tags matching the provided query. Args: tag_query: partial or full tag name to search for limit: the maximum number of tags to return |
| list_all_tagsA | List all tags sorted by number of posts and most recent post. |
| get_by_slug_or_urlB | Get a post by its slug or URL. Args: identifier: the slug, URL, or path fragment to search for |
| get_by_date_rangeB | Get posts published within a date range. Args: start_date: the start date in ISO format (YYYY-MM-DD) end_date: the end date in ISO format (YYYY-MM-DD) limit: the maximum number of posts to return |
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 7 tools
Most tools have distinct purposes focused on different retrieval methods (by date, slug/URL, tag, text content) and tag operations, but 'get_by_slug_or_url' and 'get_by_text' could potentially overlap if users confuse slug/URL with text content queries. The descriptions help clarify, but there's minor ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (e.g., get_by_date_range, list_all_tags, search_tags). The naming is predictable and readable throughout the set, with no deviations in style.
With 7 tools, this is well-scoped for a library/blog content server. It covers core retrieval operations and tag management without being overwhelming, and each tool serves a clear purpose in the domain.
The toolset provides good read/search coverage for blog content and tags, but lacks any create, update, or delete operations, which are notable gaps for a full CRUD lifecycle. Agents can retrieve and rebuild but not modify content, limiting workflow completeness.