Skip to main content
Glama

generate_place

Generates a background place image without people using Higgsfield and applies it as a shot's background. First call returns the price; confirm to spend credits.

Instructions

Make a background picture (a place, no people) with Higgsfield and make it the shot's background. 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. For the style's own places use place with a preset (free); for a free drawn place use draw_place; 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_place"
  }
}

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.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing real cost behavior: the first call spends nothing and returns only price and remaining credits, and nothing is generated until confirm: true. It also sets expectations about latency (~50 s) and the fallback for long runs — exactly the context annotations cannot carry.

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?

It is a single dense paragraph with no filler, and the most decision-relevant facts (what it makes, that it costs credits, the confirm handshake) are front-loaded. The middle clause about the 50 s wait and picture_status is slightly buried inside the same run-on sentence, costing a little scannability.

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?

For a 9-parameter, cost-incurring, open-world generator with no output schema, the definition covers the things an agent would otherwise get wrong: that the call is billable, that confirm gates spending, how long to wait, and where the result lands. Alternatives are all routed, so nothing essential is missing.

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, and the description adds genuine guidance the schema lacks: it explains the confirm handshake and the credit-spend implication of the call, plus the @1/@2 reference convention used inside prompt. It says less about put/quality/name beyond what the field descriptions already state, so not a full 5.

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 concrete verb and artifact ('Make a background picture (a place, no people)') plus what it does with the result ('make it the shot's background'). It also names the three sibling alternatives (place, draw_place, put_picture) and the distinct case each covers, so an agent can separate them without opening another schema.

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?

Gives explicit when-to-use routing: preset styles go to place (free), free drawn places to draw_place, reuse to put_picture. It also states the mandatory two-step calling procedure (call without confirm, ask the person, call again with confirm: true) and the follow-up path via picture_status if the ~50 s wait expires.

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