Skip to main content
Glama

video_lip_sync

视频对口型

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

Input Schema

NameRequiredDescriptionDefault
promptNo
audio_urlNo
avatar_urlNo
callback_idNo自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / callback_id / description
      Previous value: -"自定义追踪 ID,webhook URL 后台配置"New value: +"自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)"
  2. First observed

TDQS

D1.6/5.0
Behavior2/5

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

The annotations declare the safety properties (readOnlyHint=false, openWorldHint=true), and the definition adds no behavioral context: it does not say whether execution is asynchronous, that a work ID must be polled via get_work_status or batch_get_work_status, which permissions or quotas apply, or what happens on failure.

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

Conciseness2/5

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

The definition is one short phrase with no wasted words, but it is under-specified rather than concise. There is no structure to lead an agent to required inputs or follow-up steps.

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

Completeness1/5

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

This tool is a 4-parameter generative task marked openWorldHint=true. It has no output schema and an undocumented asynchronous workflow, yet the definition explains none of this, so it is far from complete enough for an agent to invoke the tool correctly.

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

Parameters1/5

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

Only callback_id has a schema description (25% coverage), and the tool definition supplies no information about prompt, audio_url, or avatar_url. It does not clarify that a source video/avatar and an audio track are needed, or give their formats or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"视频对口型" only restates the tool name (video_lip_sync) in Chinese, and it almost exactly repeats the schema's own description. It does not say what the task produces or how it differs from siblings such as video_character_swap or video_translate.

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

Usage Guidelines1/5

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

The definition gives no guidance on when to use this tool, when not to use it, which sibling to use instead, or what inputs are required. An agent facing more than 30 sibling tools has no basis for selecting this one.

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