Skip to main content
Glama

Choose a face photo

show_face_picker
Read-onlyIdempotent

Show saved face photos, No face photo, optional style references, and a new-image upload. Call before create_generation for a rendered run unless the user said in this chat which face to use or to use none; having a saved face photo is not a choice. After the card shows, stop and wait for the user's choice; do not draft titles or thumbnail ideas of your own. Selection returns chosen asset IDs to chat; it does not start a generation. Reads the connected account only.

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": "show_face_picker"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoface
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
nextStepYes
nextCursorYes
artifactExpiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / nextStep
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "items",
      -  "nextCursor",
      -  "artifactExpiresAt"
      -]New value: +[
      +  "items",
      +  "nextCursor",
      +  "artifactExpiresAt",
      +  "nextStep"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, and the description adds real value beyond them: selection returns chosen asset IDs to chat rather than launching a generation, and it reads only the connected account. The stop-and-wait pause is a genuine behavioral trait not encoded anywhere in the annotations. It stops short of describing pagination behavior for the cursor.

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 what the card contains, then routing condition, then the stop-and-wait rule, then what a selection returns. Every sentence carries a distinct instruction, though the middle sentence packs three conditions with semicolons and reads as a run-on.

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?

An output schema exists, so the return contract does not need spelling out, and the description still notes that selection yields asset IDs. Combined with annotations covering safety, the definition gives an agent enough to invoke correctly; the only real gap is any light guidance on limit/cursor for larger asset libraries.

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% for three parameters, so the description must carry the burden and largely does not. It gestures at the role distinction by naming face photos and optional style references, which loosely maps to the role enum values face and style_ref, but limit and cursor are never mentioned and no default or page-size behavior is explained.

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?

The description gives a specific verb and resource: it presents a chooser card containing saved face photos, a 'No face photo' option, optional style references, and a new-image upload. It also names the sibling tool it feeds into (create_generation), so an agent can tell this apart from show_thumbnails or list_asset_images 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?

Explicit when-to-use and when-not-to-use are both present: call it before create_generation for a rendered run, unless the user already stated a face or 'none' in this chat, and having a saved photo is explicitly not the same as the user choosing it. It also prescribes the follow-up behavior (stop and wait; do not draft titles or thumbnail ideas), which is the exact guidance an agent needs at the decision point.

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