Skip to main content
Glama
MCP OpenStack Operations Server

MCP OpenStack Operations Server

by E1i2e1122

get_resource_monitoring

Read current project allocations and visible hypervisor capacity to support inventory and capacity planning, separating quota limits from physical resources and excluding live utilization metrics.

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.

Returns: Resource monitoring data in JSON format with cluster summary, hypervisor details, and usage statistics.

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/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 meaningful work: it discloses that values are allocations rather than live utilization, that null is returned for unavailable capacity or incomplete flavor data, and that physical totals and project quotas have different scopes. It omits any mention of permissions or identity scope needed to see "visible" capacity.

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?

The scope statement is front-loaded and the bulleted function list is scannable. The closing "Returns:" paragraph largely restates fields already covered by the output schema, which is the one piece of expendable text.

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?

For a zero-parameter read tool with an output schema and no annotations, the description supplies the essential interpretive caveats (allocation vs. utilization, null semantics, scope mismatch warning). The only real gap is authorization/scoping expectations for what capacity is 'visible'.

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 clarify beyond the schema; this is the baseline case.

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?

Opens with a specific verb+resource ("Read current project allocations and visible hypervisor capacity") and explicitly carves out what it does not report ("not live CPU or memory utilization"). It never names the sibling tools it overlaps with (get_hypervisor_details, get_usage_statistics, get_quota), so differentiation is implicit rather than explicit.

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

Usage Guidelines4/5

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

"Use for current inventory and capacity planning" gives a clear intended context, and "No historical trends or telemetry samples are collected" functions as a de facto exclusion steering agents away from it for time-series needs. It stops short of naming which alternative tool to use instead when historical data is wanted.

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