Skip to main content
Glama
Sign In

Fashio AI

by com.fashiolabs
OverviewDiscussionsAdmin

Delete a saved template set

delete_template_set

Permanently deletes one of your saved style presets and returns {success: true}; there is no undo. Get the id from list_template_sets (or from create_template_set's response). Only the preset is removed; images already generated with it are kept. Fashio's curated sets from list_ready_template_sets cannot be deleted. 404 if the id does not exist or belongs to another account. 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

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": {
      "id": "<id>"
    },
    "name": "delete_template_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPreset id from list_template_sets (or the id create_template_set returned).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Preset id from list_template_sets (or the id create_template_set returned)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: permanence with no undo, the exact return shape ({success: true}), preserved side artifacts (generated images), 404 semantics, Bearer auth requirement, 401 for missing/revoked keys, 429 at the daily request cap, and that the call is free of diamonds. That is unusually complete disclosure for a destructive operation.

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?

Front-loaded with the destructive semantics ('Permanently deletes... there is no undo') and every sentence carries distinct information about scope, id provenance, exclusions, error codes, or cost. The final sentence packs auth, rate-limit, and pricing into one chain, which is dense but not wasteful.

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 one-parameter destructive tool with no annotations or output schema, the description covers everything an agent needs: irreversibility, what survives the delete, which sets are protected, where the id comes from, auth, rate limiting, and error conditions.

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 description coverage is 100% and the single 'id' parameter is already documented in the same terms the description uses (an id from list_template_sets or create_template_set). The description adds only provenance context that largely duplicates the schema, so the baseline 3 applies.

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 ('Permanently deletes one of your saved style presets') and immediately scopes what is and is not affected: the preset is removed but images already generated with it are kept, and curated sets from list_ready_template_sets cannot be deleted. This distinguishes it cleanly from create_template_set, list_template_sets, and any tool touching ready-made sets.

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?

Explicitly says where the required id comes from (list_template_sets or create_template_set's response) and names a hard exclusion (Fashio's curated sets from list_ready_template_sets cannot be deleted), plus the 404 condition for ids that don't exist or belong to another account. An agent knows exactly when this tool applies and when it will fail.

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