Skip to main content
Glama

CreateHQ Image Studio

pet_holiday_portraits

A studio holiday portrait set of one pet, the same animal in every frame. Send one clear front-facing photo in pet_photo; extra side or back shots of the same pet carry the body and the coat. Choose a holiday — Christmas, Thanksgiving, Halloween, Weihnachten, Noël, Navidad, お正月, 春节, Día de los Muertos, Carnaval, Diwali, Birthday or Everyday — and a studio look; the holiday sets the props, the wardrobe piece and the mood. Set structure asks for close-ups, mid shots and full-lengths by count. Up to 3 pictures per call. Costs 2 credits per picture (4 for HD) from the connected account.

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": {
      "pet_photo": "<pet_photo>"
    },
    "name": "pet_holiday_portraits"
  }
}

Input Schema

NameRequiredDescriptionDefault
holidayNoEach pick is one country's holiday, named in its own language — Weihnachten, Noël, お正月, 春节, Diwali. It sets the props, the small wardrobe piece and the mood; Everyday keeps the frame to the studio and the pet alone. Default: Christmas (US/UK).
qualityNoHD doubles the credit cost.
close_upNoHow many Close-up pictures. Each row is one picture, in this order — two close, two mid and two full-length make the six-photo set.
mid_shotNoHow many Mid shot pictures. Each row is one picture, in this order — two close, two mid and two full-length make the six-photo set.
pet_photoYesOne clear, front-facing photo of the face — a phone shot at home is fine; side or back shots of the same pet are welcome and carry the body and the coat. Send each file as a data URL (data:image/jpeg;base64,…), up to 3. PNG, JPEG or WebP.
full_lengthNoHow many Full-length pictures. Each row is one picture, in this order — two close, two mid and two full-length make the six-photo set.
studio_lookNoThe ground and the light. The props and the wardrobe come from the holiday above. Default: Red seamless.
aspect_ratioNo3:4 is the portrait print; 1:1 crops to an avatar; 16:9 suits a banner. Default: 3:4.
wardrobe_notesNoClothes and props that must be there, or anything that has to stay visible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly does so: it discloses cost (2 credits per picture, 4 for HD, charged to the connected account) and the 3-picture per-call limit, both of which are operational facts an agent needs before invoking. It does not describe latency, whether generation is synchronous, or what the response contains, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence front-loads purpose well and the credit/limit line is efficient. However, a full sentence and a half is spent re-enumerating thirteen holiday values and re-explaining pet_photo input formats that the enum and schema descriptions already state verbatim, which is padding in an otherwise compact definition.

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 generation tool with no output schema, the definition covers the essentials: source photo requirements, how counts map to shots, cost, and the per-call cap. It leaves the return shape implicit (the agent must infer that pictures come back) and says nothing about what happens if the photo is rejected, but nothing critical to calling it correctly is absent.

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 coverage is 100%, so the baseline is 3 and the schema already explains every parameter, including the holiday enum with defaults and the row-per-picture count semantics. The description adds one genuinely useful clarification — that the holiday drives props, wardrobe and mood while studio_look drives ground and light — but otherwise restates the enum values (Weihnachten, Noël, お正月, 春节...) and the pet_photo data-URL guidance already present in the schema.

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?

The description names a concrete deliverable — a studio holiday portrait set of one pet, the same animal in every frame — and the credit/picture count makes it clear this generates images. It never names or distinguishes itself from the siblings generate_image or creator_cover, so an agent cannot tell from the text alone which of the three to pick.

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

Usage Guidelines3/5

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

It gives strong prerequisites and usage mechanics (send one clear front-facing photo in pet_photo, side/back shots carry body and coat, up to 3 pictures per call) and a hard ceiling. What's missing is routing: there is no statement of when to choose this over generate_image or creator_cover, nor any exclusion or failure condition beyond the photo requirement.

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