Skip to main content
Glama
Sign In

Fashio AI

by com.fashiolabs
OverviewDiscussionsAdmin

Get one ready-made photoshoot set

get_ready_template_set

Fetches one set from Fashio's curated photoshoot library by id and returns {templateSet: {id, displayNames, description, coverUrl, tags, shotCount, shots: [{id, shotType, framing, previewUrl, thumbUrl, isDefault}]}}. Use it to inspect a set's shots and pick shotIds for create_catalog_job; list_ready_template_sets already returns the same fields, so skip this if you have them. Your own saved presets (list_template_sets) are a different kind of id and will not resolve here. 404 if the id is unknown or the set is no longer available. 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": "get_ready_template_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReady set id from list_ready_template_sets, e.g. 'set_editorial_04'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Ready set id from list_ready_template_sets, e.g. 'set_editorial_04'."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the exact return shape, 404 on unknown/unavailable ids, free cost (no diamonds), Bearer API key requirement, and both failure codes (429 daily cap, 401 missing/revoked key). It doesn't mention pagination or latency, but neither is really applicable to a single-id fetch, so the remaining gap is minor.

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?

One dense but well-ordered paragraph: purpose and return shape first, then usage/routing, then error and auth behavior. The inline return-type notation is verbose, but since there is no output schema it earns its place; nothing here is filler.

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 single-parameter read tool with no annotations and no output schema, the description covers everything an agent needs: what comes back, how to route between sibling list/get tools, cost, auth, and the specific error codes. Nothing material is missing.

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 coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema: it states that the id comes from the curated ready-set library, that list_ready_template_sets produces valid ids, and that list_template_sets preset ids are a different kind of id and will fail. That's genuine disambiguation the schema alone doesn't convey.

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: 'Fetches one set from Fashio's curated photoshoot library by id'. It also distinguishes this from the two nearest siblings by naming list_ready_template_sets and clarifying that list_template_sets ids are a different id space that will not resolve here.

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 when to use it (inspect a set's shots and pick shotIds for create_catalog_job) and when to skip it ('list_ready_template_sets already returns the same fields, so skip this if you have them'). The negative case about saved preset ids not resolving is an additional exclusion an agent would otherwise hit as a 404.

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