Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Resource Monitoring

get_resource_monitoring

Read current project flavor allocations and visible hypervisor capacity for inventory and capacity planning, keeping quota limits separate from physical totals.

Instructions

Read current project allocations and visible hypervisor capacity.

Functions:

  • Report project flavor allocations, not live CPU or memory utilization

  • Collect hypervisor statistics and resource allocation

  • Separate project quota limits from visible physical capacity

  • Return null for unavailable capacity or incomplete flavor allocations

Use for current inventory and capacity planning. No historical trends or telemetry samples are collected. Physical totals and project allocations have different scopes and should not be divided into a utilization rate. For measured CPU/memory utilization, load, or trends, use get_gnocchi_measures instead; never present these allocations as usage.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: values are allocations rather than live measurements, project quota scope differs from physical capacity scope, and missing data is returned as null rather than fabricated. It does not state permission requirements or whether the call is strictly side-effect free, though the opening "Read" verb strongly implies the latter.

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?

Front-loaded with the core read statement, then scoped by bullets, then closed with the anti-pattern warning and alternative. The bullet list is slightly redundant with the opening sentence, but each line adds a distinct caveat about scope or null handling.

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

Completeness5/5

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

For a zero-parameter inventory tool with an output schema already documenting return shape, the description supplies exactly the missing layer: what the numbers mean, what they must not be compared against, and where to go for actual utilization data. Nothing needed to call it correctly is absent.

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 there is nothing for the description to disambiguate; baseline is 4. The description correctly spends its words on output semantics instead of inventing parameter guidance.

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

Purpose5/5

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

Opens with a specific verb+resource+scope: "Read current project allocations and visible hypervisor capacity." The bullet list further disambiguates what is returned (flavor allocations, hypervisor statistics) versus what is not (live CPU/memory utilization), so an agent can distinguish it from get_gnocchi_measures and the hypervisor detail tools without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ("Use for current inventory and capacity planning"), explicit when-not ("No historical trends or telemetry samples are collected"), and a named alternative for the excluded case ("For measured CPU/memory utilization, load, or trends, use get_gnocchi_measures instead"). It also warns against a specific misuse (dividing allocations by physical totals to derive a utilization rate).

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