Skip to main content
Glama

ai_actor_perform

演员演出(系统演员或 Persona)

actor_id 既可为系统演员 ID,也可为自定义 Persona 的 actor_id,共用同一套演出参数与异步任务响应。

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

Input Schema

NameRequiredDescriptionDefault
speedNo
styleNo
scriptNo
actor_idNo系统演员 ID,或 Persona 的 actor_id
stabilityNo
similarityNo
callback_idNo自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)
auto_emotionNo
speaker_boostNo

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

C2.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write. The description adds a genuinely valuable behavioral fact beyond them: the call is asynchronous and returns a task response. It still omits permissions, cost/quota, failure behavior, and how to retrieve results, which matter for a task-generating operation.

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?

Two short lines, front-loaded with the action and then the actor_id nuance; no filler. It is under-specified rather than padded, so conciseness itself is not the weakness.

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 9-parameter, zero-required, non-idempotent task-creation tool with no output schema, and the description never explains what happens with omitted parameters, what the task response contains, or how to poll for completion. Given the schema only covers a fifth of the parameters, far more prose is needed for an agent to invoke it correctly.

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 only 22% across 9 parameters; only actor_id and callback_id are documented in the schema, and the description merely restates the actor_id duality already present there. Seven parameters (speed, style, script, stability, similarity, auto_emotion, speaker_boost) get no meaning, ranges, defaults, or interaction notes from either source.

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

Purpose3/5

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

The description states a verb-plus-resource ('actor performance' for a system actor or Persona) and clarifies that both actor_id kinds share the same parameters and async task response. However, '演出' is a broad verb and nothing distinguishes this from siblings like ai_actor_say or ai_actor_list, so an agent cannot route confidently from the text alone.

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

Usage Guidelines2/5

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

It implicitly says the tool works for both system actors and custom Personas, which is mildly useful selection context, but gives no when-to-use vs. when-not guidance and names no alternative (e.g., ai_actor_say for speech-only output). The async nature is mentioned but no polling/status-check workflow is suggested.

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