Skip to main content
Glama
MCP OpenStack Operations Server

MCP OpenStack Operations Server

by E1i2e1122

get_server_events

Retrieve recent events for an OpenStack server by name or UUID to monitor actions, results, and completion status. Optionally include per-action details.

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. First observedv0.1.0

TDQS

B3.3/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 burden; "Get" implies a read, but the description never says so explicitly, nor does it describe the recency window, ordering, or pagination behavior. It does add one genuinely useful behavioral safeguard — warning that instance_name is the only accepted identifier key — which prevents a common malformed call, but the remaining operational profile is thin.

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?

Short and front-loaded: the purpose sentence comes first, followed by the calling convention. The second sentence is slightly redundant ("no server_id parameter" then "do not use server_id or instance_id"), but the repetition is defensible for a known failure mode and costs little.

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

Completeness3/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 no explanation here, and the parameter naming guidance is covered. What is missing is the context that makes the tool callable with confidence: what constitutes an "event," how far back "recent" reaches, and when this tool is preferable to the instance-detail siblings.

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, and the description still earns credit by clarifying that instance_name accepts either a name or a UUID and by explicitly ruling out server_id and instance_id. That naming guidance is meaning the schema does not convey. It says nothing about limit or include_event_details, but those are already documented in 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") plus the accepted identifier forms, which is well above tautology. It does not, however, distinguish itself from adjacent siblings such as get_instance_details or get_instance, so an agent must infer that this is the event/action-history view rather than the server record itself.

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

Usage Guidelines2/5

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

The description only tells the agent how to call it, not when to choose it over the many sibling get_* tools. There is no statement of the scenario that selects this tool (e.g., troubleshooting a server's recent actions) and no exclusions, leaving usage entirely implied by the name.

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