Skip to main content
Glama

video_upscale

视频超分

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

Input Schema

NameRequiredDescriptionDefault
video_urlNo
callback_idNo自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)
workspace_idNo

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

D1.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond them: no mention of asynchronous job submission, polling behavior, or what happens to the supplied video. It does not contradict the annotations, but it contributes no extra behavioral context.

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?

Four characters contain no filler, but the definition is under-specified rather than concise. There is no front-loaded explanation of what the tool produces or how to invoke it correctly.

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?

This is an asynchronous, open-world media-generation tool with three parameters and no output schema. The description says nothing about job creation, result retrieval via get_work_status, or the callback_id round-trip that the schema hints at. For that complexity, it falls far short of adequate.

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?

Schema description coverage is only 33%: callback_id is documented inline, but video_url and workspace_id have no descriptions at all. The tool description does not compensate, saying nothing about accepted URL formats, size limits, or workspace scoping. The low-coverage case requires the description to fill this gap, and it does not.

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

Purpose2/5

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

"视频超分" (video super-resolution) merely restates the tool name video_upscale in Chinese. It doesn't name the input (a video URL), the output, or how it differs from close siblings like video_enhance_v2. The four-character description is a near-tautology, providing no distinguishing detail beyond the name itself.

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 when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as video_enhance_v2 or fetch_video_from_link. An agent choosing among the many video_* siblings has zero routing information from this description.

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