Skip to main content
Glama
Sign In
Seedream/Seedance MCP Server

Seedream/Seedance MCP Server

by nsmao-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

action-imitation

Generate character animations by describing a reference action, target character, and desired style for video content creation.

Instructions

Ark-only 模式下不支持该工具

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": {
      "referenceAction": "<referenceAction>",
      "targetCharacter": "<targetCharacter>",
      "style": "<style>"
    },
    "name": "action-imitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceActionYes参考动作描述
targetCharacterYes目标角色描述
styleYes动作风格

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

D1.4/5.0
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. The statement 'Ark-only 模式下不支持该工具' suggests the tool may be unavailable or non-functional in certain contexts, but provides no information about what the tool actually does, its effects, limitations, or operational behavior when it IS supported.

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?

While technically concise (one sentence), the description is under-specified rather than appropriately concise. It fails to provide any functional information about the tool, making it ineffective despite its brevity. The single sentence doesn't earn its place as it doesn't describe the tool's purpose or usage.

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?

The description is completely inadequate for a 3-parameter tool with no annotations and no output schema. It provides no functional information about what the tool does, when to use it, or what results to expect. Given the complexity suggested by the name 'action-imitation' and three required parameters, this description fails to provide any meaningful context.

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?

The schema description coverage is 100%, with all three parameters (referenceAction, targetCharacter, style) having clear descriptions in the input schema. The tool description adds no additional parameter information beyond what's already documented in the schema, so the baseline score of 3 is appropriate.

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

Purpose1/5

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

The description 'Ark-only 模式下不支持该工具' (This tool is not supported in Ark-only mode) provides no information about what the tool actually does. It's a restriction statement rather than a functional description, making it completely misleading about the tool's purpose. The name 'action-imitation' suggests some form of action replication, but the description contradicts this by stating it's unsupported.

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 description provides no guidance on when to use this tool. It only states that it's not supported in a specific mode, but gives no information about when it IS supported or appropriate to use. There's no comparison to sibling tools or indication of the tool's intended use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools