Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Server Events

get_server_events

Retrieve recent OpenStack server events by name or UUID to troubleshoot changes or track action results; optionally fetch event details and completion times.

Instructions

Get recent events for a server by name or UUID.

Pass either value using instance_name, for example get_server_events(instance_name=""). There is no server_id parameter; do not use server_id or instance_id as argument names.

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": {
      "instance_name": "<instance_name>"
    },
    "name": "get_server_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of events to return (default: 50)
instance_nameYesName or ID of the server instance
include_event_detailsNoFetch per-action event details to report completion times and results. This makes one additional Nova API request per returned action and caps the effective limit at 10.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.6.7
    • addedInput schema / properties / include_event_details
      Added value: +{
      +  "default": false,
      +  "description": "Fetch per-action event details to report\ncompletion times and results. This makes one additional Nova API\nrequest per returned action and caps the effective limit at 10.",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changedv3.5.8
    • addedInput schema / properties / instance_name / description
      Added value: +"Name or ID of the server instance"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of events to return (default: 50)"
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the 'recent' scope and the naming trap, but says nothing about permissions, ordering/recency window, or pagination beyond the limit parameter already in the schema, leaving real behavioral gaps for an unannotated tool.

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?

Two short, front-loaded paragraphs with no filler; the second paragraph is a purposeful guardrail. The name-or-UUID restatement mildly duplicates the schema wording.

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?

An output schema exists so return values need not be explained, and the cost tradeoff of include_event_details is documented in the schema. For a three-parameter, unannotated read tool the description is nearly sufficient, missing only safety/prerequisite context.

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 genuine value by warning that server_id and instance_id are not valid argument names and by giving a concrete call example. The one-off cost/cap behavior of include_event_details is left to 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?

States a specific verb and resource ('Get recent events for a server') and constrains the lookup key to name or UUID. That is clearly distinct from read tools like get_instance or get_server_volumes, though the description never explicitly contrasts with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent how to call the tool (pass the identifier via instance_name) but never says when to reach for it over alternatives or what prerequisites apply. Usage is implied by the 'recent events' framing rather than stated.

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