Skip to main content
Glama
vigneshgopalandd-maker

Drake Lyrics MCP

by vigneshgopalandd-maker
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion. The purpose of write_drake_bars is clearly described and distinct.

    Naming Consistency5/5

    With a single tool, the naming is trivially consistent. The name write_drake_bars follows a clear verb_noun pattern and accurately conveys functionality.

    Tool Count4/5

    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.

    Completeness5/5

    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.

  • Average 3.9/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 1 commit in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior4/5

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

    Given no annotations, the description carries the burden of explaining behavior. It discloses the output type ('short Drake-style lyrics') and the input ('what the user is going through'). This is honest about the tool being a text generation tool, though it could add nuance about creative liberties or tone.

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

    Conciseness4/5

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

    The description is a single, front-loaded sentence that conveys the core function. The second sentence 'Pass what the user is going through' is slightly redundant and could be clearer, but it is still concise. No wasted words, though the wording 'Pass' is a bit awkward.

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

    Completeness4/5

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

    For a low-complexity tool with one required parameter and no output schema, the description is sufficiently complete. It explains the input and output without needing to elaborate on return values or side effects. A minor gap is lack of specificity about 'Drake-style' (e.g., tone, length), but that is likely understood.

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

    Parameters3/5

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

    Schema coverage is 100% with a clear description for the 'situation' parameter. The description adds the phrase 'Pass what the user is going through,' which rephrases the parameter's purpose but adds little new meaning beyond the schema's own example. The schema does the heavy lifting, so a 3 is appropriate.

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

    Purpose5/5

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

    The description clearly states the tool's function: 'Turn a situation or topic into short Drake-style lyrics.' This is specific with a verb ('turn') and resource ('situation/topic... into lyrics'). It distinguishes itself as a creative generation tool, and since there are no sibling tools, there is no ambiguity.

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

    Usage Guidelines3/5

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

    The description implies when to use the tool (when the user wants Drake-style lyrics based on a situation), but does not explicitly state exclusions or alternatives. With no sibling tools, there is no need for comparison, yet a clearer 'use when...' statement would improve guidance.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

drake-mcp MCP server

Copy to your README.md:

Score Badge

drake-mcp MCP server

Copy to your README.md:

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/vigneshgopalandd-maker/drake-mcp'

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