Skip to main content
Glama

AI Rap Generators

generate_rap_lyrics

Draft a short original English rap verse about a topic. Shares the 10 free daily lyric drafts with the birthday tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "generate_rap_lyrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNotrap
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden. It does disclose a real behavioral trait the schema cannot: a quota of 10 free daily lyric drafts shared with the birthday tool, plus that output is short, original, and in English. It omits what happens when the quota is exhausted (error vs. degradation) and gives no permission or latency context.

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?

Two compact sentences with no filler, and the core purpose is front-loaded. The quota sentence is slightly cryptic in placement but is short enough not to harm readability.

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

Completeness2/5

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

For a two-parameter generation tool with no annotations and no output schema, the definition is thin. It does not explain the output shape beyond 'short short verse,' gives no example, and leaves the style parameter entirely undocumented, leaving the agent to infer the most consequential tuning knob.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and largely does not. The word 'topic' maps to the required topic parameter and the enum values for style are self-explanatory in the schema, but the description never mentions the style parameter, its default of trap, or how style affects the verse.

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

Purpose4/5

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

States a concrete verb and resource: 'Draft a short original English rap verse about a topic.' The phrase 'with the birthday tool' signals a related sibling exists, though it is framed around shared quota rather than distinguishing the two purposes. An agent can still tell this is the general-purpose rap verse generator.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no indication of when to prefer generate_birthday_rap_lyrics or the name generators instead. The only usage-adjacent information is the shared 10-draft daily limit, which is a constraint rather than selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.