Skip to main content
Glama

Prepare a Character Studio identity or look

prepare_character_builder

Author one private Character Builder image and prepare its exact quote without spending. Supply structured traits, outfit, scene and output settings. Unspecified fields use the current Builder defaults; custom descriptions express details outside the offered choices. Identity and style references require exact owned image asset IDs from list_media or reference import. To make a look, use the exact saved characterId; its identity traits and original are preserved while outfit, hair and scene can change. Use list_saved_characters and get_saved_character to disambiguate names. Quality and format use the same live Builder pricing as the app. Show the returned recipe, exact USD total and expiry, then obtain explicit approval before confirm_character_builder. Every changed recipe or reference requires a new quote. The result retains a real Builder recipe and can be saved on request using save_character.

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

Input Schema

NameRequiredDescriptionDefault
traitsNo
formatModeNo
outputModeNo
characterIdNo
qualityModeNo
advancedNotesNo
outputOptionsNo
consistencyModeNo
referenceImagesNo
mustRemainVisibleNo
referenceStrengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, non-destructive, non-idempotent call. The description goes well beyond that by disclosing the no-spend quote behavior, quote expiry, the approval gate before confirmation, quote invalidation on recipe change, and that saved-character identity traits and the original are preserved. These are exactly the operational facts an agent needs before calling.

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?

Front-loaded with the purpose plus the no-spend guarantee, and nearly every sentence adds a distinct rule. It is dense and paragraph-free for a nine-sentence block, so the workflow constraints (approval, re-quote, save) are harder to scan than they could be.

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 an 11-parameter nested tool with no output schema, the description covers the workflow, pricing, defaults, reference provenance and persistence path. It partially describes the return ('recipe, exact USD total and expiry') but does not characterize the shape of the authored image result or how the recipe is presented for approval.

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?

With 0% schema description coverage the description has to carry parameter meaning, and it does a lot: 'structured traits, outfit, scene and output settings', unspecified fields falling back to Builder defaults, custom* strings as escape hatches for choices outside the enums, referenceImages requiring owned ma_ asset IDs, and characterId semantics for saved identities. Gaps remain for consistencyMode, referenceStrength, mustRemainVisible, outputMode and the outputOptions booleans, which are only loosely covered by 'output settings'.

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 opening sentence gives a specific verb and resource: 'Author one private Character Builder image and prepare its exact quote without spending.' It immediately separates this tool from confirm_character_builder (the spending step) and save_character (persistence), so an agent can place it in the workflow without reading sibling schemas.

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

Usage Guidelines5/5

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

Explicit routing is provided for each branch: use list_media or reference import for asset IDs, list_saved_characters and get_saved_character to disambiguate names, confirm_character_builder only after explicit approval, and save_character to persist. It also states the condition that triggers a re-quote: 'Every changed recipe or reference requires a new quote.'

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.