Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Image Detail List

get_image_detail_list

Get detailed list of all images with comprehensive metadata.

Instructions

Get detailed list of all images with comprehensive metadata.

Functions:

  • List all images available in the project

  • Show image status, size, and format information

  • Display image properties and metadata

  • Provide ownership and visibility details

Use when user requests image listing, image information, or image metadata details.

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

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, include every image Glance shows the credential, including other projects' private images (like 'openstack image list' as an administrator); rows carry project_id and project_name. Requires ALLOW_CROSS_PROJECT_READ=true on the server. Public images are visible to everyone, so check scope.warning.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.9.2
    • addedInput schema / properties / all_projects
      Added value: +{
      +  "default": false,
      +  "description": "If True, include every image Glance shows the credential,\nincluding other projects' private images (like 'openstack image\nlist' as an administrator); rows carry project_id and project_name.\nRequires ALLOW_CROSS_PROJECT_READ=true on the server. Public images\nare visible to everyone, so check scope.warning.",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the burden, and it does communicate that this is a non-mutating enumeration returning status/ownership/visibility fields. It omits the most consequential behaviour though: that cross-project rows require the server-side ALLOW_CROSS_PROJECT_READ flag and that scope.warning should be checked — a detail left entirely to the schema.

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

Conciseness3/5

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

The lead sentence is front-loaded and clear, but the four "Functions" bullets are near-synonyms of it ("Detailed list" restated as "List all images", "Show image status", "Display image properties", "Provide ownership") and consume space without adding discriminative information. The structure is readable but padded.

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?

For a single-optional-parameter read-only listing with an output schema handling return values, the description plus schema cover what an agent needs to call it correctly. The only meaningful gap is that cross-project scoping is not hinted at in prose, forcing the agent into the schema for the one behaviour that could surprise it.

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% for the single optional `all_projects` flag, so the schema fully documents its default and the server-flag precondition. The description adds no parameter meaning of its own, which is acceptable but not additive — the baseline 3 applies.

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 opening sentence gives a specific verb and resource ("Get detailed list of all images") plus scope ("comprehensive metadata"), and the bullets name the concrete fields surfaced: status, size, format, ownership, visibility. It does not explicitly distinguish itself from near-neighbours such as get_image_members, so it stops short of a 5.

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?

"Use when user requests image listing, image information, or image metadata details" gives a clear triggering intent. However, it offers no exclusions, no prerequisites, and no pointer to any alternative tool for related image operations, leaving the agent to infer boundaries on its own.

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