Drake Lyrics 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_drake_barsA | Turn a situation or topic into short Drake-style lyrics. Pass what the user is going through. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| drake_mode | Wrap a situation so the model writes (or asks for) Drake-style bars. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| style-guide | How this server writes Drake-style lyrics. |
| ui://drake/drake-app.html |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion. The purpose of write_drake_bars is clearly described and distinct.
With a single tool, the naming is trivially consistent. The name write_drake_bars follows a clear verb_noun pattern and accurately conveys functionality.
While the server has only one tool, the scope is extremely narrow (generating Drake-style lyrics). The single tool fully addresses this purpose, though the count is slightly below the typical range.
For its stated domain, the tool fully covers the only required operation. There are no obvious gaps in functionality for generating Drake-style lyrics from a topic.