Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Hypervisor Details

get_hypervisor_details

Retrieve detailed hypervisor information from OpenStack, including all hypervisors or a specific hypervisor by name or ID, to support monitoring and operations.

Instructions

Get detailed information about hypervisors

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

Input Schema

NameRequiredDescriptionDefault
hypervisor_nameNoName/ID of specific hypervisor or "all" for all hypervisorsall

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / hypervisor_name / description
      Added value: +"Name/ID of specific hypervisor or \"all\" for all hypervisors"
  2. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden, yet it says nothing about read-only semantics, required permissions, whether hypervisor data is live or cached, or failure modes for an unknown hypervisor name. The presence of an output schema offsets only slightly.

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 front-loads the verb and resource with zero padding. It is terse to the point of under-specification, but nothing in it is wasted.

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?

An output schema exists, so return value explanation is not required, but for a tool with no annotations the description leaves the agent without permission requirements, error behavior, or selection context relative to the sibling detail-getters. It is thin for anything beyond the simplest call.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter already documents the name/ID-or-"all" semantics, so the schema does the work. The description adds no meaning beyond it, which matches the baseline 3 for high-coverage schemas.

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?

States a verb ("Get") and resource ("hypervisors"), so the subject matter is identifiable. However, "detailed information" is vague about what details are returned, and nothing distinguishes it from the many sibling get_*_details tools beyond the resource noun.

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?

No guidance on when to use this tool, no prerequisites, and no mention of alternatives such as listing versus fetching a single hypervisor. The agent must infer usage entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.