Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Gnocchi Measures

get_gnocchi_measures

Read stored Gnocchi telemetry time series for a metric to analyze measured utilization, load, trends, and historical values.

Instructions

Read stored Gnocchi measures (telemetry time series) for a metric.

Use for measured utilization, load, trends, and history ("CPU usage of vm1", "memory over the last hour"). Values are observed telemetry collected by Ceilometer, such as cpu, memory.usage, or disk and network counters. Cumulative counters like cpu (nanoseconds) grow over time; compare consecutive values for rates. Some metrics such as vcpus and memory record flavor sizes, not usage. For averages, totals, top N, or groups across many resources, use get_gnocchi_aggregates. For allocations, capacity, or quotas, use get_resource_monitoring or get_quota. If a metric is not collected, report that; do not substitute allocation data.

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": {
      "metric": "<metric>"
    },
    "name": "get_gnocchi_measures"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopNoExclusive ISO 8601 stop time
limitNoMaximum latest measures to return (1-1000, default 100)
startNoInclusive ISO 8601 start time (default: all retained data)
metricYesMetric UUID, or a metric name when resource_id is given
refreshNoProcess pending measures before reading
resampleNoResample interval in seconds (requires granularity)
aggregationNoAggregation method from the archive policy (default mean)mean
granularityNoGranularity in seconds from the metric archive policy
resource_idNoResource ID (Nova server UUID for instances)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.8.3

TDQS

A4.3/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 substantial work: it discloses that values are Ceilometer-observed telemetry, that cumulative counters like cpu (nanoseconds) grow over time and require consecutive-value comparison for rates, and that some metrics (vcpus, memory) record flavor sizes rather than usage. It does not cover permissions, pagination behavior, or read-cost, which keeps it from a 5.

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 purpose and the aggregate alternative are front-loaded, and the parenthetical examples earn their place by tying the tool to realistic queries. It is slightly longer than necessary, with interpretive caveats about cumulative counters and flavor sizes arriving after the alternative-tool routing.

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 9-parameter read tool with a full output schema, the description covers purpose, alternatives, and interpretation pitfalls adequately; return-value explanation is correctly omitted because an output schema exists. Minor gaps remain around permissions and how start/stop interact with limit and resampling.

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%, so the schema already documents all nine parameters including start/stop, limit, resample, aggregation, and granularity; baseline is 3. The description adds interpretive meaning about metric values (cumulative counters, flavor-size metrics) but does not clarify parameter interaction, such as that resample requires granularity — that constraint lives only in the schema.

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?

The description opens with a specific verb and resource: 'Read stored Gnocchi measures (telemetry time series) for a metric.' It further distinguishes itself from sibling tools by naming get_gnocchi_aggregates, get_resource_monitoring, and get_quota with the conditions that select them.

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 routing guidance is given for three alternatives (aggregates for averages/totals/top N/groups, resource_monitoring or quota for allocations/capacity/quotas) plus a clear negative instruction: 'If a metric is not collected, report that; do not substitute allocation data.' This is exactly the when/when-not/alternative structure that earns a top score.

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