Skip to main content
Glama

List talking-head sets

list_talking_head_sets
Read-only

Curated background sets for talking_head_keyframe.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile needs no repetition. Beyond that the description adds nothing: no statement about whether the set list is static or workspace-dependent, its size, ordering, or that results are safe to cache. The word 'curated' is the only extra signal.

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?

A single fragment with no filler, and the key linkage to `talking_head_keyframe` is front-loaded. It is arguably over-compressed as a fragment with no verb, which slightly weakens scanability compared with one complete sentence.

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?

Complexity is low and an output schema exists, so return shape need not be described. What is missing is the calling context an agent actually needs: that no inputs are required and this is the discovery step preceding `talking_head_keyframe`. That gap is small but real for an otherwise trivially simple tool.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; baseline is 4. The description correctly implies the tool is a parameterless enumeration rather than suggesting any filtering inputs.

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 identifies the resource ('curated background sets') and ties it to the consuming sibling 'talking_head_keyframe', so an agent knows this supplies the set list for that tool. The verb is only implied by the tool name 'list_talking_head_sets', and it does not explicitly distinguish itself from the other list_* siblings, keeping it short of a 5.

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?

The reference to `talking_head_keyframe` implies this is a lookup to perform before calling that generation tool, which gives usable context. However, there is no explicit when-to-use statement, no exclusion of alternatives, and no statement that this takes no parameters and needs no prior state.

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