Skip to main content
Glama
Sign In

Fashio AI

by com.fashiolabs
OverviewDiscussionsAdmin

List saved template sets

list_template_sets

Lists the style presets YOU saved on this account with create_template_set and returns {templateSets: [{id, label, toolId, images, pose, shotType, stylePreset, ratio, coverUrl, sourceMediaId, ...}]} (empty if none). Use it to find a templateSetId for create_generation or an id for delete_template_set. Use list_ready_template_sets instead to browse Fashio's curated photoshoot library for create_catalog_job; the two kinds of ids are not interchangeable. Returns every preset in one response (no paging, no guaranteed order). Free (no diamonds). Needs a valid Fashio API key (Bearer); every call counts toward the key's daily request cap (429 when reached, 401 for a missing or revoked key).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_template_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so thoroughly: no paging, no guaranteed ordering, free of diamond cost, Bearer API key required, and explicit 429/401 failure modes tied to the daily request cap. That is exactly the operational context an agent needs before calling.

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?

Content is front-loaded: purpose first, then return shape, then routing guidance, then operational constraints. The inline JSON return sketch is dense but earns its place because no output schema exists. Minor deduction for packing return shape and routing advice into one long run-on sentence rather than separate lines.

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?

For a zero-parameter list tool with no annotations and no output schema, the description covers purpose, return fields, sibling routing, cost, auth, and rate-limit behavior. Nothing material is missing for correct invocation.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing parameter-level left to clarify. The description instead documents the response shape, which is useful but not a parameter concern.

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 verb and resource ("Lists the style presets YOU saved on this account with create_template_set") and explicitly separates it from the curated library returned by list_ready_template_sets. An agent can distinguish it from every sibling without opening a schema.

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 concrete when-to-use guidance tied to specific downstream tools (find a templateSetId for create_generation, or an id for delete_template_set) and names the alternative for the other case (list_ready_template_sets for create_catalog_job). It even warns that the two kinds of ids are not interchangeable, which prevents a realistic misuse.

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

All Fashio AI toolsInspect
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.

Resources