Skip to main content
Glama

generate_character

Creates a full-body character picture with the background removed and adds it to a shot's cast, showing the credit price first so the person can confirm before spending.

Instructions

Make a character picture with Higgsfield (whole body, background taken off) and add it to a shot's cast, or replace a member's picture with replace. Spends the person's Higgsfield credits: the first call (without confirm) only returns the price and credits left; ask the person, then call again with the same arguments and confirm: true. Waits up to about 50 s; if it isn't done, call picture_status. put: media or none keeps it out of the shot. For objects or other kinds use generate_picture; for a free drawn character in the style use draw_character; to reuse one made before use put_picture.

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": {
      "prompt": "<prompt>"
    },
    "name": "generate_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
putNoWhere it goes: shot (into the shot), media (the project's Media bin), none (only the generated pictures list).
nameNoA short name for it in the project.
shotNoShot id (from get_project). Default: the shot on screen.
promptYesWhat to draw, in plain words. @1, @2 point at the reference pictures in order.
confirmNotrue only after the person agreed to the price.
qualityNoDefault 2k. About 1.5 / 2 / 3 Higgsfield credits.
replaceNoA cast member id in that shot whose picture this replaces.
referencesNoPaths of up to 4 pictures on this computer to keep the same person or thing.
from_picturesNoIds of pictures made before (generated_pictures) to use as references.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / put / description
      Added value: +"Where it goes: shot (into the shot), media (the project's Media bin), none (only the generated pictures list)."
    • changedInput schema / properties / quality / description
      Previous value: -"Default 2k."New value: +"Default 2k. About 1.5 / 2 / 3 Higgsfield credits."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the call spends Higgsfield credits, that the first call without confirm is a price-only dry run requiring a second confirming call with identical arguments, that it waits ~50 s, and that picture_status should be used on timeout. The destructiveHint=false/openWorldHint=true annotation pair does not convey cost, latency, or the dry-run pattern, so this is genuine added value.

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-loads what the tool makes, then cost/confirm, then timing, then sibling routing — a sensible order. It is dense but nearly every clause carries operational information; the fragment 'put: media or none keeps it out of the shot' is slightly telegraphic, and the ~50 s/latency sentence could flow better.

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 9-parameter, credit-spending, non-idempotent mutation with no output schema, it covers cost, confirmation flow, timeout handling, placement, and alternatives — the essentials. Minor gaps remain: it never says what a successful call returns (e.g., a picture id usable with put_picture or from_pictures), which matters since there is no output schema.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by explaining the confirm semantics as a two-call negotiation ('ask the person, then call again with the same arguments and confirm: true') and by clarifying that put values media or none keep the result out of the shot. It does not cover name, references, or from_pictures, which the schema already documents.

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?

States a specific verb and resource plus the resulting effect: 'Make a character picture with Higgsfield (whole body, background taken off) and add it to a shot's cast, or replace a member's picture with replace.' The parenthetical output characteristics and the two modes (add vs. replace) make it unmistakable against siblings like generate_picture or draw_character.

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?

Explicitly routes the agent: generate_picture for objects or other kinds, draw_character for a free drawn character in the style, put_picture to reuse one made before. It also prescribes when to use which mode ('put: media or none keeps it out of the shot') and the two-step confirm protocol, leaving little to inference.

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