Digital Guitar Archive MCP Server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_guitar_archiveC | Search the Digital Guitar Archive for records. Supports full-text search and field-specific filters. |
| get_record_detailsC | Get full details for a specific record by its ID |
| list_sourcesB | Get a list of all source libraries (RISM sigla) in the archive with record counts and location info |
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 with no overlap: get_record_details retrieves a specific record, list_sources provides metadata about source libraries, and search_guitar_archive performs queries across the archive. The descriptions clearly differentiate between individual record access, source cataloging, and search functionality.
All three tools follow a consistent verb_noun pattern with snake_case naming: get_record_details, list_sources, and search_guitar_archive. The naming is predictable and follows the same structural convention throughout the tool set.
With only 3 tools, the server feels somewhat thin for an archive management domain. While the tools cover basic access patterns (get, list, search), typical archive operations like creating, updating, or deleting records are missing, suggesting the surface may be incomplete rather than optimally scoped.
For a digital archive server, there are significant gaps in CRUD/lifecycle coverage. The tools only provide read-only operations (get, list, search) with no ability to create, update, or delete records. This will cause agent failures when trying to perform basic archive management tasks beyond querying existing data.