Skip to main content
Glama

Avatar from a preset

generate_preset

Makes an avatar from the user's own photo with a genframe preset and scene (see list_presets). Charged like one picture. Use only a photo of the user themself or of someone who agreed.

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": {
      "preset": "<preset>"
    },
    "name": "generate_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoScene id from list_presets (default: the first).
presetYesPreset id from list_presets.
captionNoText on the poster for scenes with a caption; empty string = no text.
photo_urlNoThe person's photo: public https URL or a link from this server.
aspect_ratioNoDefault 4:5.
photo_job_idNoOr one of the user's genframe pictures.

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?

Annotations already tell the agent this is a non-readonly, non-idempotent, non-destructive open-world call, so the safety profile is covered. The description adds real value on top: the cost model ("Charged like one picture") and the consent restriction on the input photo, both of which are invisible in the structured fields. It still omits what actually comes back — an immediate image or a job to poll via get_job — which matters for a metered, non-idempotent generation call.

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?

Three short sentences, front-loaded with the action and ending with the constraint; nothing is padded. "Charged like one picture" is slightly compressed idiom that could be read as ambiguous about the currency of the charge, which is the only real deduction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 burden of saying what the call yields, and it is silent on whether the result is a finished image, a job id for get_job, or a listing entry. For a metered, non-idempotent generation tool with an open-world network hint, that is a meaningful gap. The cost and consent notes partially compensate, but the return contract is missing.

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 every one of the six parameters, including the photo_url/photo_job_id alternatives and the caption empty-string convention, is already documented in the schema. The description only echoes the preset/scene pairing and adds no format, default, or precedence detail beyond it. Baseline 3 applies.

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?

"Makes an avatar from the user's own photo with a genframe preset and scene" gives a specific verb and resource plus the distinguishing ingredient (the preset/scene pipeline), and points at list_presets as the source of ids. It falls short of 5 because it never contrasts itself with the obvious neighbour, generate_image, so an agent must guess whether a preset avatar is a special case of image generation or a separate flow.

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?

The description routes the agent to list_presets for valid ids and states a hard eligibility rule ("only a photo of the user themself or of someone who agreed"), which is genuine usage guidance. It says nothing about when this should be chosen over generate_image, generate_video, or upscale_image, and gives no prerequisites beyond the preset lookup.

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