Skip to main content
Glama
Sign In

Fashio AI

by com.fashiolabs
OverviewDiscussionsAdmin

List selectable poses

list_poses

Lists active poses in catalog order and returns {poses: [...]}. Pass a pose's id as pose in create_generation (required for pose_angle_switch; optional for virtual_model, outfit_photo, jewelry_on_model) or create_template_set. Without type you get the default non-jewelry pose set, not every pose; pass a jewelry type for jewelry_on_model poses. No paging: only the first limit poses come back. 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_poses"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoPose set: omit for the default (non-jewelry) poses, or ring | necklace | earring | bracelet for jewelry poses.
limitNoHow many to return, 1-100 (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many to return, 1-100 (default 20)."
    • changedInput schema / properties / type / description
      Previous value: -"e.g. ring/necklace/earring/bracelet for jewelry poses."New value: +"Pose set: omit for the default (non-jewelry) poses, or ring | necklace | earring | bracelet for jewelry poses."
  2. 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 present, the description carries the full burden and does so: it discloses there is no paging (only the first `limit` poses return), that the call is free (no diamonds), that a valid Bearer API key is required, and that every call counts toward a daily cap with 429/401 failure modes. That is cost, auth, rate-limit, and truncation behavior in one place.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and return shape, then usage, then caveats, then cost/auth. Every clause carries information an agent needs; nothing is repeated from the title or schema verbatim for its own sake.

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?

For a simple two-parameter read tool with no output schema, the description covers purpose, routing, cost, and failure modes well, and it is clear the returned objects contain an `id`. It stops short of describing what other fields a pose object carries, which is the only meaningful gap.

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 baseline is 3, but the description adds genuine meaning the schema lacks: `type` omission silently yields a subset rather than all poses, and `limit` is a hard truncation rather than a page size. Those are behavioral gotchas beyond the property descriptions.

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 active poses in catalog order') and even the return shape ({poses: [...]}). It also distinguishes itself from siblings by naming where the results are consumed (create_generation, create_template_set), so an agent knows this is the prerequisite lookup rather than a mutating tool.

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?

Explicit routing guidance: pass a pose id as `pose` in create_generation, required for pose_angle_switch and optional for virtual_model, outfit_photo, jewelry_on_model, or into create_template_set. It also gives an explicit when-not: without `type` you get only the default non-jewelry set, not every pose, so jewelry poses require a jewelry type.

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