Skip to main content
Glama

Headshot

headshot

A professional headshot of the person in face_file (or a saved character) in a curated style and/or with explicit controls (list_headshot_styles).

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

Input Schema

NameRequiredDescriptionDefault
notesNo
aspectNo3:4
controlsNo
face_fileNo
character_idNo
style_item_idNo
confirm_creditsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations mark this as a non-read-only, non-destructive, non-open-world generation operation, but the description adds little beyond the basic input concept. It does not mention credit consumption, the purpose of `confirm_credits`, whether generation is asynchronous and requires `wait_for_generation`, or what happens when both `face_file` and `character_id` are supplied. With minimal annotation coverage, these behavioral gaps are significant for an agent invoking a paid generation tool.

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?

The description is compact and front-loads the core concept: a professional headshot from a face file or saved character. It contains no filler or repetition. The sentence-fragment style and backtick references are slightly awkward but do not impede understanding.

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?

This is a complex generation tool with seven parameters, no schema descriptions, and meaningful cost/async behavior. The output schema may cover return values, but the description omits critical invocation context such as credit confirmation, waiting for completion, and most parameter semantics. It is not complete enough for an agent to call the tool confidently without inspecting the schema and inferring missing behavior.

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 must compensate for all seven undocumented parameters. It adds meaning for `face_file` and `character_id` by explaining the face-or-saved-character source, and gestures at `style_item_id`/`controls` through curated styles and explicit controls. But `aspect`, `notes`, and `confirm_credits` receive no explanation, and the relationship between style and controls remains vague.

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?

The description clearly identifies the output as a professional headshot generated from `face_file` or a saved character, optionally using a curated style or controls. It is distinguishable from `list_headshot_styles` by pointing to that sibling as the style lookup. However, it lacks an explicit verb such as 'generate' and does not distinguish itself from broader generation siblings like `generate` or `product_shot`.

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?

It implies when to use the tool: when you have a face file or saved character and want a styled headshot. The pointer to `list_headshot_styles` is useful for discovering styles. But there is no explicit guidance on when to prefer this over `generate`, `cast_swap`, `product_shot`, or `try_on`, and no exclusions or prerequisites are stated.

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