Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Gnocchi Resources

get_gnocchi_resources

Lists, searches, or shows current-project Gnocchi telemetry resources and their metric maps so you can identify available metrics before reading measures.

Instructions

List, search, or show current-project Gnocchi (telemetry) resources.

Resources are the objects Ceilometer measures, such as instances, disks, and network interfaces. Each resource maps metric names to metric IDs. Use this to find which metrics exist for a server before reading measures.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum resources or revisions to return (1-1000, default 100)
markerNoPagination marker from a previous next_marker value
filtersNoJSON object of attribute equality filters for listing, for example {"display_name": "vm1"} or {"original_resource_id": "..."}
historyNoWith resource_id, return the resource's revision history
resource_idNoResource ID; for instances this is the Nova server UUID. When set, returns that resource with its metrics map.
resource_typeNoGnocchi resource type (generic, instance, instance_disk, instance_network_interface, ...; default generic)generic

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.8.3

TDQS

A3.6/5.0
Behavior3/5

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

There are no annotations, so the description bears the disclosure burden: it correctly states the data is current-project scoped and explains the returned structure (a metrics map, and a single resource with its metrics map when resource_id is set). It says nothing about permissions, pagination behavior across pages, or how history mode changes results, which are meaningful gaps for a telemetry query tool with no annotations.

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?

Three short sentences, with the action and scope front-loaded and the domain explanation and usage hint following. Every sentence carries information; there is no filler or repetition of the tool name.

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 six optional parameters, full schema coverage, and an output schema that carries return-value documentation, the description covers purpose, domain meaning, project scoping, and one key usage pattern. It could say more about how listing interacts with filters and pagination, but nothing essential to invoking it is missing.

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 limit, marker, filters, history, resource_id, and resource_type, making 3 the baseline. The description corroborates the resource_id behavior and the metrics-map return, but adds no semantics or syntax for filters, history, or resource_type beyond what the schema supplies.

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?

The description opens with a specific verb set (list, search, show) and a named resource (current-project Gnocchi telemetry resources), and it defines what a resource is and how it maps metric names to metric IDs. It does not explicitly name sibling tools like get_gnocchi_measures or get_gnocchi_metrics, but the phrase 'before reading measures' implicitly separates it from the measures 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 a clear use case: find which metrics exist for a server before reading measures, which nudges an agent toward this tool before get_gnocchi_measures. It lacks explicit exclusions or a statement of when to use get_gnocchi_metrics or aggregates instead, so it stops short of full routing guidance.

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