Skip to main content
Glama
Sign In
H3 Cloud MCP

H3 Cloud MCP

by lst016
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

h3_art_list_workflows

Lists reviewed AutoDL Art H3 workflows with categories, required media, and resolutions so users can choose a compatible workflow for generation.

Instructions

List 18 reviewed AutoDL Art H3 workflows, categories, media requirements and resolutions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 full burden; it implies a read-only enumeration and discloses the catalog size (18) and the kinds of metadata returned. It does not explicitly confirm it is side-effect free, nor mention auth, caching, or freshness of the 'reviewed' set, though for a zero-parameter listing the behavioral surface is small.

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?

A single front-loaded sentence with the verb first and no filler. Every element (count, namespace, returned facets) carries information an agent needs.

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

Completeness4/5

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

With zero parameters and an output schema covering the return shape, the description needs only to establish purpose and scope, which it does. Adding a hint about the likely next step (quote_workflow/generate_workflow) would make it fully complete.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals the tool is argument-free by framing it purely as a listing operation.

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?

Specific verb (List) plus resource (AutoDL Art H3 workflows) and an enumeration of what the catalog contains: categories, media requirements, resolutions. It clearly reads as a discovery/enumeration tool distinct from the per-workflow siblings (h3_art_quote_workflow, h3_art_generate_workflow), though it never names them explicitly.

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?

Usage is only implied: an agent can infer this is the first step before quoting or generating a specific workflow, but the description never says when to call it or what to do instead. No exclusions, prerequisites, or alternative paths are stated.

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