Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Gnocchi Service Info

get_gnocchi_service_info

Retrieve Gnocchi service configuration and health details to verify supported metric granularities, aggregation methods, resource types, and measure-processing backlog for alarms or queries.

Instructions

Read Gnocchi service configuration and health information.

Use to check which granularities and aggregation methods a metric supports (for get_gnocchi_measures or set_alarms), which resource types exist, and whether measure processing is backlogged.

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

Input Schema

NameRequiredDescriptionDefault
sectionsNoComma-separated subset of archive_policies, archive_policy_rules, resource_types, capabilities, status (default: all). status usually requires an admin role.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.8.3

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Read' signals a non-mutating operation and the content categories are disclosed, but permission requirements (the admin-role note for 'status' lives only in the schema) and any cost or latency of pulling all sections are not stated in the description itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler: the capability statement comes first, followed by the concrete diagnostic use cases. Every clause maps to an actual calling scenario.

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 present, return values need not be explained, and the single optional parameter is fully covered by the schema. The description supplies purpose and triggering scenarios adequately; only permission/behavioral framing for the admin-gated 'status' section is left to the schema.

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 coverage is 100% and the schema already documents the comma-separated section list, the 'all' default, and the admin-role caveat for 'status'. The description's mention of granularities, aggregation methods, resource types and backlog loosely maps to section values but adds no syntax or format detail beyond the schema.

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 names a specific verb and resource ('Read Gnocchi service configuration and health information') and immediately enumerates what is retrievable: granularities, aggregation methods, resource types, and processing backlog. That distinguishes it from data-fetching siblings like get_gnocchi_measures or get_gnocchi_aggregates, though it never names those siblings explicitly as alternatives.

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 concrete use cases tied to downstream tools: 'Use to check which granularities and aggregation methods a metric supports (for get_gnocchi_measures or set_alarms)' plus backlog checking. This is genuine when-to-use guidance, but there is no when-not guidance or statement about cost/redundancy versus other service-info tools.

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