Skip to main content
Glama
Sign In

Rizz Ipsum

by com.rizzipsum
OverviewDiscussionsAdmin

Rizz filler text

generate
Read-only

Generate rizz-flavored placeholder text (Gen Z, Gen Alpha, Gen X, or Millennial) as filler for mockups and layouts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of units, from 1 to 50. Defaults: 3 sentences / 25 words / 1 paragraph. Unknown fields are rejected.
flavorNoDialect. Defaults to genz.
formatNoUnit of output. Defaults to sentences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / count / description
      Previous value: -"Number of units. Defaults: 3 sentences / 25 words / 1 paragraph."New value: +"Number of units, from 1 to 50. Defaults: 3 sentences / 25 words / 1 paragraph. Unknown fields are rejected."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, non-open-world, non-destructive operation. The description adds that the output is placeholder text for mockups and layouts, but it does not disclose randomness, output shape, or other operational traits beyond what the schema and annotations already provide. It does not contradict the annotations.

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

Conciseness5/5

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

The description is a single well-formed sentence with no wasted words. The core action and use case are front-loaded.

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 simple three-parameter generation tool with full schema coverage and clear safety annotations, the description is largely complete: it names the output as placeholder text and gives the intended use. A minor gap is that it does not mention sibling routing or generation behavior, but those are not essential for correct invocation here.

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 description coverage is 100%, and the schema documents defaults, enums, and count limits. The description only restates the flavor categories and does not add meaning for count or format beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description gives a specific verb and resource: generate rizz-flavored placeholder text. It also lists the flavor categories and the intended use for mockups and layouts. It does not explicitly distinguish itself from the sibling rizzipsum.open, which keeps it from 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 Guidelines4/5

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

The phrase "as filler for mockups and layouts" clearly states the intended context for using the tool. It does not say when not to use it or name an alternative, so it falls short of explicit routing guidance.

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

All Rizz Ipsum toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources