Skip to main content
Glama

Your outfits

list_outfits
Read-onlyIdempotent

Your saved outfits (looks), newest first, optionally for one character. Pass an id as lookId to dress the character in it when generating.

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_outfits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
characterIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral value with the 'newest first' ordering, but says nothing about pagination, default size, or whether filtering by a character with no outfits returns empty versus error.

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

Conciseness3/5

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

Short and front-loaded, with the resource and ordering stated first. However, the second sentence is spent on a lookId argument the tool does not accept, which is both wasted space and a source of misuse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should convey what a returned outfit record contains and how many come back by default; it only says 'outfits (looks)'. Combined with an undocumented limit parameter and a phantom lookId, it is not complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries full burden, and it only loosely covers one parameter ('optionally for one character' maps to characterId, whose type and maxLength are undocumented). It says nothing about 'limit' (default 20, max 50), and it instructs the agent to 'Pass an id as lookId' — a parameter that does not exist in the schema, which is actively misleading.

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?

States the resource plainly ('Your saved outfits (looks)'), plus ordering ('newest first') and an optional filter ('for one character'). An agent can distinguish it from list_characters or list_media by resource alone, though the verb (list/retrieve) is only implied by the name and title rather than the description.

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

Usage Guidelines3/5

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

Gives implied context: use it to see saved looks, optionally narrowed to a single character, and hints at a downstream generation use case. It never states when to prefer this over a sibling (e.g. list_characters) or any exclusions, so guidance is inferred rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources