Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Gnocchi Metrics

get_gnocchi_metrics

List or show current-project Gnocchi telemetry metrics, including archive policy and unit, to verify which series are collected before reading measures or creating alarms.

Instructions

List or show current-project Gnocchi metrics.

Without arguments, lists metric names and IDs of current-project resources. With resource_id, shows that resource's metrics including archive policy and unit. With metric, shows one metric. Use it to check which telemetry metrics are actually collected before reading measures or creating alarms. These are measured telemetry series, not allocations or quotas.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum metrics to return (1-1000, default 100)
metricNoMetric UUID, or a metric name such as cpu or memory.usage when resource_id is also given
resource_idNoResource ID (Nova server UUID for instances)
resource_typeNoGnocchi resource type used for listing (default generic)generic

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.8.3

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the read-only 'current-project' scope and what each mode returns (names and IDs versus archive policy and unit), but it says nothing about pagination beyond the limit parameter, error behavior, or permissions. It is adequate but not rich.

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 description is front-loaded with the purpose and then organizes the three modes in a parallel structure, so it is easy to scan. There is minor redundancy in restating what each parameter does, but no sentence is wasted.

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?

With an output schema available, return values need no explanation, and all four parameters are documented. The description also covers the tool's modes and scope. The only missing piece is behavioral detail, such as error paths, which would matter more if no output schema existed.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds the relational semantics that the schema states only implicitly: that no arguments produce a list, that resource_id switches to a per-resource view, and that metric narrows to a single series. The interaction between metric and resource_id is also clarified in prose.

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 pairs a specific verb ('List or show') with a specific resource (current-project Gnocchi metrics) and then enumerates the three invocation modes: no arguments, resource_id, and metric. The closing sentence ('measured telemetry series, not allocations or quotas') distinguishes this tool from the sibling aggregates tool.

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?

It gives explicit when-to-use guidance ('check which telemetry metrics are actually collected before reading measures or creating alarms'), which points the agent toward the right workflow stage. It does not state when to use it instead of the sibling get_gnocchi_resources, but that is the only notable guidance gap.

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