Skip to main content
Glama

Ready-made creators

list_ready_made_creators
Read-onlyIdempotent

The Creator Library: ready-made characters with a finished identity sheet (and often a voice) that you can add to your characters for free with add_ready_made_creator. Filter by niche (for example fitness, beauty, food, tech, fashion) or gender. Shows which ones you already added.

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": "list_ready_made_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
nicheNo
genderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral detail – that listings flag which creators are already added and that adding is free – but says nothing about pagination or ordering beyond the schema's limit default.

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 that front-load the resource and follow with filters and the adopt path. The parenthetical niche examples are useful rather than filler; nothing needs cutting, though the sentence packing a few ideas could be split for scannability.

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?

No output schema exists, so the description carries the return-shape burden and does say entries show existing adoption status. For a three-optional-parameter read-only list tool this is nearly complete; only pagination and result volume are unaddressed.

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 0%, so the schema gives names, types, defaults, and bounds without semantics. The description compensates partly by naming the filterable dimensions (niche with examples, gender) and the 'already added' marker, but leaves limit's paging behavior and whether niche does exact or partial matching unexplained.

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: lists ready-made creators from a 'Creator Library', with what each entry contains (identity sheet, often a voice) and the free-add path. That distinguishes it from siblings like list_characters or get_character, though the differentiation is implied rather than explicit.

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?

Gives clear context for use: browse the library, then call add_ready_made_creator to adopt one, and filter by niche or gender. It does not explicitly say when not to use it versus list_characters, so it falls short of full alternative routing.

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.

Resources