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

anime-video-mcp

by Simonxz578
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_assets

Generates media assets from project directories for anime video shorts and romance series, then reports pending media providers or QA gates.

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

Input Schema

NameRequiredDescriptionDefault
project_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.1/5.0
Behavior1/5

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

No annotations exist, so the description carries the full burden of behavioral disclosure. 'Report pending media provider or QA gate' does not state side effects, whether the operation is read-only, whether it triggers background work, or what the returned state means. This is critically underspecified.

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 one-sentence description is short, but it is under-specified rather than concise. Every word should earn its place; here the sentence is confusing and does not provide enough operating detail to be called appropriately structured.

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?

With no annotations, no output schema, and a misleading one-line description, the tool is not adequately described for an agent to invoke it correctly. Even though there is only one required parameter, the overall behavior, purpose, and expected output remain unclear.

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 schema has 0% description coverage for the single required parameter 'project_dir', and the description does not mention this parameter at all. The description adds no meaning beyond the parameter name, so it does not compensate for the missing schema documentation.

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 is misleading: the tool name 'generate_assets' implies asset generation, but the description says 'Report pending media provider or QA gate.' The verb and object do not clearly explain what the tool actually does, and no sibling differentiation is provided.

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?

There is no guidance on when to use this tool versus what to do. It does not mention alternatives or clarify whether it should be called before/after creating episodes, generating voice/music, or QA. The agent is left without any decision support.

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