Skip to main content
Glama
Sign In
H3 Cloud MCP

H3 Cloud MCP

by lst016
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

h3_job_status

Check whether a queued H3 video has finished processing and list its ComfyUI output files.

Instructions

Check whether a queued H3 video has finished and list its ComfyUI output files.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does reveal the useful fact that the response includes ComfyUI output files, but says nothing about job states (queued/running/failed), behavior for an unknown job_id, or whether the call is a safe read.

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?

One tightly written sentence that front-loads the core action and adds the return-content detail. Nothing is wasted and there is no filler.

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 one-parameter, annotation-free, no-output-schema tool, the description conveys purpose and roughly what comes back. It still leaves gaps an agent needs: where to obtain job_id and how to interpret non-finished states.

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% for the single parameter; job_id has no description in either schema or prose. The description does not say where job_id comes from (presumably the h3_generate response) or what format it takes, so the coverage gap is not compensated.

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?

Concrete verb+resource: checks completion of a queued H3 video job and lists its ComfyUI output files. It is distinguishable from most siblings (h3_generate, h3_cancel_job), though it never contrasts itself with the near-identical h3_art_job_status sibling.

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 words "queued" and "has finished" imply the polling-after-submission usage, but there is no explicit guidance on when to call it versus h3_art_job_status or how often to poll. Usage must be inferred rather than read.

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