Skip to main content
Glama
Sign In
MCP_HCL

MCP_HCL

by cheese-sansan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hcl_capabilities

Check verified H3C Cloud Lab capabilities and the activation boundary to determine which MCP_HCL operations can stage topology changes before opening the project in HCL.

Instructions

Describe verified capabilities and the activation boundary.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 burden of behavioral disclosure, and it says nothing about side effects, permissions, or whether this is a safe read. The word 'verified' hints that some capabilities may be unverified, but that distinction is never explained.

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?

A single short sentence with the object stated up front and no filler. It is efficient, though the brevity comes at the cost of the detail that would make it actionable.

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?

An output schema exists, so return values need not be described in prose, which relieves much of the burden. Still, with no annotations and abstract terminology, the definition leaves an agent unsure what 'activation boundary' refers to or when invoking this tool is the right move.

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 zero parameters, so per the rubric the baseline is 4. There is nothing for the description to clarify on the input side.

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

Purpose3/5

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

The description has a verb ('Describe') and an object ('verified capabilities and the activation boundary'), so it is not a tautology. However, 'capabilities' and 'activation boundary' are abstract domain terms with no concrete indication of what is actually returned or what area of the API this covers, so an agent cannot confidently distinguish its scope from siblings like hcl_inspect_project.

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

Usage Guidelines2/5

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

There is no guidance on when to call this tool, when not to, or which sibling to prefer. The sibling names (hcl_list_projects, hcl_inspect_project, hcl_stage_add_device, hcl_stage_link) suggest an orchestration workflow where a capability-check step would matter, but the description does not connect itself to that flow.

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