Skip to main content
Glama

AI Rap Generators

generate_birthday_rap_lyrics

Draft a short English birthday rap verse using a name and a personal detail. Includes 10 free drafts per day.

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": {
      "name": "<name>",
      "detail": "<detail>",
      "relationship": "<relationship>"
    },
    "name": "generate_birthday_rap_lyrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
detailYes
relationshipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and it does disclose one real behavioral trait: a quota of 10 free drafts per day. It says nothing about what happens when the quota is exhausted, whether the output is generated deterministically, or any auth/plan requirement, so the disclosure is partial.

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 short sentences with the core action front-loaded and zero filler. The quota sentence is slightly awkwardly attached ("Includes...") but still earns its place as useful constraint information.

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

Completeness3/5

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

For a three-required-parameter generation tool with no annotations and no output schema, the definition is minimally adequate. It leaves the required relationship parameter and any notion of output shape (how short is "short") undocumented, which an agent would need to know to call it correctly.

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 for all three required parameters. It covers "name" and "personal detail" implicitly, but the required "relationship" parameter — the one with an enum of best-friend/couple/family/coworker/kid-friendly that materially changes tone — is never mentioned.

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 specific verb and resource ("Draft a short English birthday rap verse") plus the inputs used, which distinguishes it from generic lyric or name generators by the birthday-verse scope. It does not explicitly name how it differs from the sibling generate_rap_lyrics, so it falls short of a 5.

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 the usage context (birthday rap verse from a name and a personal detail) but gives no explicit when-to-use vs when-not guidance and never points to generate_rap_lyrics as the general-purpose alternative. The agent must infer the choice from the tool's own name and phrasing.

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.