Skip to main content
Glama

Virtual Try-On

sirv_try_on_garment

Creates a virtual try-on image by placing a garment from one photo onto a person from another, ideal for clothing listings.

Instructions

Show the garment from one image on the person in another image.

Use it for clothing listings. Do not use it for products that are not worn (use sirv_place_product_in_scene) or to change the person or the scene (use sirv_edit_image).

Inputs: both are required: person_image_url, a photo of the person or model, and garment_image_url, a photo of the garment.

Neither source image changes. Returns result_url, the try-on image.

Credits: spends workspace credits. The cost depends on the model and options.

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": {
      "person_image_url": "<person_image_url>",
      "garment_image_url": "<garment_image_url>"
    },
    "name": "sirv_try_on_garment"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_image_urlYesPublic URL of a photo of the person or model
garment_image_urlYesPublic URL of a photo of the garment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that neither source image is modified and that the call spends workspace credits with cost varying by model/options — material for a non-idempotent, billable operation. It does not cover retry/latency behavior or whether the returned result is persisted, so it stops short of full behavioral disclosure.

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

Conciseness5/5

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

Front-loads the core operation, then routing rules, then inputs, then side effects, with no filler sentences. Each block (purpose, exclusions, inputs, side effects, cost) earns its place.

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?

With no output schema, the description correctly supplies the return value (result_url), and it adds the credit-cost caveat and the non-mutation guarantee. For a two-parameter, annotation-covered tool, an agent has everything needed to select and call it.

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% and both parameters already carry descriptions, so the baseline is 3. The description's restatement ('both are required', 'a photo of the person or model') largely duplicates the schema and adds no format, sizing, or URL-validity guidance beyond it.

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 operation on specific resources: composite the garment from one image onto the person in another. It also names the two sibling tools it is not (sirv_place_product_in_scene, sirv_edit_image), so an agent can discriminate without opening 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?

Gives an explicit positive case ('use it for clothing listings') and two explicit exclusions, each paired with the correct alternative and the condition that selects it. Nothing about tool selection is left to inference.

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