Skip to main content
Glama
Sign In
anime-video-mcp

anime-video-mcp

by Simonxz578
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_voice

Generate voiceover audio for anime video shorts and romance chapter series, providing spoken narration for offline video production.

Instructions

Report pending media provider or QA gate.

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": {
      "project_dir": "<project_dir>"
    },
    "name": "generate_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1/5.0
Behavior1/5

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

With no annotations, the description must fully disclose behavior. It does not mention side effects, prerequisites, or what the tool returns. The text is cryptic and adds no behavioral context beyond the confusing statement.

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

Conciseness1/5

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

While the description is very short, it is not concise in a useful way—it is under-specified and misleading. It fails to provide any actionable information and does not front-load key details.

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?

For a tool with one parameter, no output schema, and no annotations, the description should at least clarify its function. This description is completely inadequate and leaves the agent without any understanding of how 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?

The single parameter project_dir is not described in the schema (0% coverage), and the description offers no explanation of its meaning or format. The agent has no information about what to pass.

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 'Report pending media provider or QA gate' does not align with the tool name 'generate_voice'. It gives no indication of what the tool actually does, and the verb 'report' is unrelated to voice generation. This is misleading and fails to establish a clear purpose.

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?

No guidance is provided on when to use this tool or how it relates to sibling tools like generate_music or render_episode. The description does not mention any alternative tools or conditions for use.

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