@avclabs.ai/enhance-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_API_KEY | Yes | API authentication key | |
| HTTP_API_BASE_URL | No | FastAPI HTTP Server address | https://mcp.avc.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskB | 创建视频增强任务（异步） 支持两种上传方式：
参数说明：
|
| get_task_statusA | 查询视频增强任务状态 |
| enhance_video_syncA | 同步增强视频（阻塞等待完成） 支持两种上传方式：
参数说明：
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: creating an async task, performing a synchronous enhancement, and querying task status. No overlap or ambiguity.
All names use snake_case and verb_noun pattern, but the verbs vary (create, enhance, get) and 'enhance_video_sync' mixes a descriptor. Mostly consistent.
Three tools is on the lower end but reasonable for a focused video enhancement service. Each tool serves a clear function without being redundant.
Covers creation and status checking, but lacks cancellation, listing all tasks, or retrieving final results explicitly. Minor but notable gaps.