Skip to main content
Glama

Roll a WOW Identity

roll_identity

Generate random quirky office-worker bot identities with rarity scores and shareable cards for AI agent customization across platforms.

Instructions

WOW — Weird Office Workers. Roll a fresh random bot identity: a quirky office-worker character with a rarity score and a screenshot-ready share card. Stores the roll for save_last_roll and get_rarity_report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
identityYes
rarityYes
paragraphYes
framedYes
loreYes
Behavior4/5

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

Annotations indicate this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds valuable context beyond annotations by specifying that it 'Stores the roll' (implying state change) and generates a 'random' identity with 'rarity score' and 'share card', which clarifies the mutation and output behavior. It does not contradict annotations, as 'Roll' implies creation (consistent with readOnlyHint=false) and storage aligns with non-idempotent.

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 front-loaded with the core action ('Roll a fresh random bot identity') and efficiently adds details in a single, well-structured sentence. Every part earns its place by clarifying the character type, output features, and storage implications without unnecessary words or repetition.

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

Completeness5/5

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

Given the tool has 0 parameters, rich annotations, and an output schema (which handles return values), the description is complete. It covers the purpose, output characteristics (rarity, share card), and interaction with siblings (storage for save_last_roll and get_rarity_report), providing all necessary context for an agent to use it effectively without over-explaining.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing on the tool's purpose and output. A baseline of 4 is applied since it compensates by explaining the output semantics (rarity score, share card) rather than redundant parameter details.

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 specific action ('Roll a fresh random bot identity') and resource ('quirky office-worker character'), distinguishing it from siblings like 'get_identity' (which likely retrieves) and 'save_last_roll' (which stores). It explicitly mentions the output includes a 'rarity score' and 'screenshot-ready share card', making the purpose highly specific and differentiated.

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 description provides clear context by stating it 'Stores the roll for save_last_roll and get_rarity_report', indicating when to use this tool (to generate a new identity) versus alternatives (e.g., use save_last_roll to store it, get_rarity_report for analysis). However, it does not explicitly state when NOT to use it or compare to all siblings like 'get_identity' or 'get_theme_for_platform', missing full alternative guidance.

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

Install Server

Other Tools

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/tjclaude88/mcp-bling'

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