Velox TriFit: Virtual Try-On API

Save a selected photo to TriFit

upload_trifit_image

Idempotent

With explicit permission, import the selected personal or clothing image into the connected TriFit account. Resizes automatically, saves it in the website library and selects its photo/product slot. Product images also use the existing cached description preparation. Never import arbitrary URLs or retry an uncertain import automatically.

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": {
      "clientImportId": "<clientImportId>",
      "role": "<role>",
      "permissionConfirmed": "<permissionConfirmed>",
      "file": "<file>"
    },
    "name": "upload_trifit_image"
  }
}

Input Schema

Name	Required	Description
`file`	Yes
`role`	Yes
`clientImportId`	Yes	New UUID for this user-approved import. Preserve it; never replace it after an uncertain outcome.
`permissionConfirmed`	Yes

Output Schema

Name	Required	Description	Default
`role`	Yes
`reused`	Yes
`status`	Yes
`assetId`	Yes
`environment`	Yes
`librarySource`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds substantive context beyond that: automatic resizing, writes to the website library, slot selection, and the cached-description path for product images. It still leaves unclear whether selecting a slot replaces or destroys a previously selected photo and what 'connected account' authentication entails, which is the one gap for a mutating tool.

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?

Four compact sentences, with the permission precondition and the core action front-loaded, followed by side effects and prohibitions. No padding, though the 'cached description preparation' clause is dense enough that it takes a read to parse.

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?

With annotations covering safety and an output schema covering returns, the description needs only to cover preconditions and side effects, and it does both. Completeness falls slightly short on slot-replacement semantics and account/auth scoping, the two things an agent could get wrong on this call.

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 description coverage is low (25%), so the description must help, and it does: it explains the personal-vs-product meaning of `role` (product images take the cached-description path), the significance of `permissionConfirmed` ('with explicit permission'), and constrains `download_url` by forbidding arbitrary URLs. It adds nothing for `file_id`, `file_name`, or `mime_type`, which remain undocumented.

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 states a specific verb and resource: import a selected personal or clothing image into the connected TriFit account, and it enumerates the downstream effects (resize, library save, slot selection). It implicitly distinguishes itself from the prepare_trifit_upload sibling by referring to 'the existing cached description preparation' as an upstream step, but it never names the sibling outright.

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

Usage Guidelines4/5

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

It gives real conditions and exclusions: requires explicit permission from the user, never import arbitrary URLs, and never retry an uncertain import automatically. That's clear when/when-not guidance, though it doesn't explicitly route the agent to prepare_trifit_upload for the preparation step or to list_trifit_library for verification.

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

All Velox TriFit: Virtual Try-On API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.