Skip to main content
Glama

Talking head: keyframe

talking_head_keyframe

Step 1 of a talking head: the person on a set (close_up | waist_up | wide; landscape | portrait). Then text_to_speech, then talking_head_video.

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": {
      "face_file": "<face_file>"
    },
    "name": "talking_head_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
formatNolandscape
framingNowaist_up
set_fileNo
face_fileYes
set_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

A3.7/5.0
Behavior3/5

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

The annotations already establish that this is not read-only, not destructive, and closed-world, and the description adds useful pipeline context. It does not disclose credit consumption or the role of confirm_credits, nor does it explain what artifact is produced, leaving meaningful behavioral gaps.

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?

The description is one compact sentence, front-loaded with the key workflow role. The parenthetical options are efficient and no wording is wasted.

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

Completeness3/5

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

The output schema and annotations reduce the description's burden for return values and safety behavior. However, for a 7-parameter generation tool with 0% schema description coverage, the omission of parameter relationships and credit-confirmation behavior leaves it only minimally complete.

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

Parameters3/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 carry parameter meaning. It adds valuable allowed values for framing and format that are absent from the schema, and it clarifies that a person and set are involved, but it leaves face_file, set_file, set_item_id, notes, and confirm_credits largely unexplained.

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 states that this is step 1 of a talking-head workflow and describes the keyframe as a person on a set with framing and format choices. It names the subsequent sibling tools, so an agent can distinguish this from text_to_speech and talking_head_video, though it never explicitly says it generates a keyframe image.

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

Usage Guidelines4/5

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

The pipeline order is explicit: use this first, then text_to_speech, then talking_head_video. That provides clear when-to-use guidance relative to the named alternatives, but it does not state exclusions or prerequisites such as required inputs beyond the schema.

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