Skip to main content
Glama
MCP OpenStack Operations Server

MCP OpenStack Operations Server

by E1i2e1122

get_usage_statistics

Retrieve project Nova allocation-hours for a date range, with server, RAM, CPU, and disk breakdowns, and keep current compute, network, and storage snapshots separate from period data.

Instructions

Get current-project Nova allocation-hours and separate current snapshots.

Functions:

  • Show project usage statistics over a specified time period

  • Display servers, RAM MB-Hours, CPU Hours, and Disk GB-Hours

  • Provide detailed server usage breakdown when available

  • Keep current compute/network/storage snapshots separate from period data

Use for project usage reports. Period data comes from Nova simple tenant usage. It measures allocation-hours, not live utilization or monetary charges. Missing or denied usage API returns failure without synthetic fallback.

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

Input Schema

NameRequiredDescriptionDefault
end_dateNoExclusive end date at UTC midnight (YYYY-MM-DD; defaults to today)
start_dateNoInclusive start date at UTC midnight (YYYY-MM-DD; defaults to 30 days ago)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses useful behavior: data comes from Nova simple tenant usage, snapshots are kept separate, and missing/denied usage API returns failure without synthetic fallback. It does not explicitly mention permissions or read-only semantics, but the key data-source and failure behavior are covered.

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 and structured with a short functions list. There is minor repetition between the opening sentence and the first bullet, but overall it is efficiently organized and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and both parameters are fully documented, the description provides enough additional context: usage-report purpose, Nova simple tenant usage source, allocation-hours semantics, snapshot separation, and failure behavior. An agent has what it needs to invoke the tool correctly.

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 date parameters, their UTC-midnight behavior, defaults, and inclusive/exclusive semantics. The description adds only general 'specified time period' context, so baseline 3 is appropriate.

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 gives a specific verb and resource: retrieving current-project Nova allocation-hours and separate current snapshots. It also distinguishes the measurement from live utilization and monetary charges, which helps separate it from monitoring-oriented siblings.

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 states 'Use for project usage reports' and clarifies that the tool measures allocation-hours rather than live utilization or monetary charges. It does not name a direct alternative sibling, but the intended context and exclusions are clear.

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