Skip to main content
Glama
Sign In
H3 Cloud MCP

H3 Cloud MCP

by lst016
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

h3_art_quote_workflow

Estimate the cost of a selected H3 workflow using observed rates, without charging or performing a live price lookup.

Instructions

Estimate one selected H3 workflow using observed rates; no charge or live price lookup.

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": {
      "workflow_id": "<workflow_id>"
    },
    "name": "h3_art_quote_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
durationNo
resolutionNo
workflow_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden; it usefully discloses that this is an estimate based on observed rates with no charge and no live price lookup. However, it omits auth requirements, error behavior, determinism, and what the estimate returns.

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

Conciseness4/5

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

It is a single front-loaded sentence with no wasted words, and the key qualifier about observed rates and no charge is placed early. The terseness contributes to gaps elsewhere but the sentence itself is well structured.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and three undocumented parameters, one sentence is not complete enough. Key context such as parameter effects, prerequisites, and return behavior is missing.

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 all three parameters, so the description must compensate but largely does not. It only vaguely implies that workflow_id identifies the selected workflow, and says nothing about what duration or resolution mean or how they affect the estimate.

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 uses a specific verb ('Estimate') and resource ('one selected H3 workflow') with a clear scope ('using observed rates'). It distinguishes the tool from a generic quote or generation tool, though it does not name a sibling alternative 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?

The phrase 'no charge or live price lookup' implies when this estimator is appropriate, but the description never explicitly says when to use it versus h3_art_quote or h3_art_generate_workflow. Usage is implied rather than 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