Skip to main content
Glama
Sign In
H3 Cloud MCP

H3 Cloud MCP

by lst016
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

h3_download_video

Download a completed H3 video via a private tunnel into H3_OUTPUT_DIR using its job ID, so you can retrieve finished generation outputs locally.

Instructions

Download a finished H3 video through the private tunnel into H3_OUTPUT_DIR.

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": {
      "job_id": "<job_id>"
    },
    "name": "h3_download_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the download goes through a private tunnel into H3_OUTPUT_DIR, but omits authentication needs, overwrite behavior, and failure handling.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no wasted words. It communicates the action and destination efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter download tool, it gives the action and output destination but leaves the required job_id unexplained and lacks return or error behavior details. It is minimally workable but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the sole required parameter job_id is not mentioned in the description. The description implies identifying a finished video but does not explain that job_id is the identifier or its expected format.

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

Purpose4/5

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

The description states a specific verb and resource: downloading a finished H3 video. It also mentions the private tunnel and destination directory, though it does not explicitly distinguish itself from the sibling h3_art_download_video.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "finished" implies the video must be complete before calling, which suggests using job-status tools first. However, no sibling alternatives or when-not conditions are named.

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