Skip to main content
Glama

Try on

try_on

Fashion photo: the garments worn by the person in person_file, or by a described model (gender Female|Male|Non-binary, age 20s…60s+).

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": {
      "garment_files": "<garment_files>"
    },
    "name": "try_on"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNo
buildNo
notesNo
aspectNo3:4
genderNo
person_fileNo
garment_filesYes
confirm_creditsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.4/5.0
Behavior2/5

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

Annotations only declare it is a non-read-only, non-destructive, closed-world call. The description adds nothing about the traits that matter for a generation tool: that it likely consumes credits (the `confirm_credits` parameter strongly implies a paid, confirmable operation), whether the result is asynchronous and must be polled via get_generation/wait_for_generation, or what happens on failure.

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?

It is short and front-loads the domain (fashion photo), but the single sentence is a fragment with awkward line breaks and backtick markup, and its brevity comes from omission rather than density. Nothing is padded, but little is communicated.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Against an 8-parameter generation tool with zero schema descriptions, a paid-credit confirmation parameter, and a likely async lifecycle, this one-line fragment is far from sufficient. An output schema exists so return values need not be explained, but input modes, credit behavior, and async handling are all missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden, yet it only touches `person_file`, `gender`, and `age`. Five of eight parameters — `garment_files` (the sole required field), `build`, `notes`, `aspect`, and especially `confirm_credits` — receive no explanation of format, allowed values, or semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase ("Fashion photo: the garments worn by...") rather than a verb+resource statement, so an agent must infer that this generates a try-on image. It does identify the key inputs (garments, a person file or a described model), but it never distinguishes this from siblings like product_shot or headshot, which is the core ambiguity for a fashion-rendering tool.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative. The only implicit routing signal is the either/or between `person_file` and a text-described model (gender/age), which hints at two modes but never says which to prefer or when to use product_shot instead.

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