Skip to main content
Glama
MCP OpenStack Operations Server

MCP OpenStack Operations Server

by E1i2e1122

get_image_members

Lists the member projects that can access a specified OpenStack image, using the image name or ID.

Instructions

List member projects for an image.

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": {
      "image_name": "<image_name>"
    },
    "name": "get_image_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_nameYesImage name or ID.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 and does not meet it. It never states that this is a read-only operation, whether it requires image ownership or admin rights, whether an empty list means the image is private, or whether results are paginated.

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?

One short, front-loaded sentence with zero padding. It is efficient, though its brevity stems partly from under-specification rather than disciplined editing.

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

Completeness2/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, and the lone parameter is fully documented. However, the concept of an image "member project" is domain-specific and goes unexplained, and with no annotations the description leaves authorization and read-only behavior entirely opaque.

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 single parameter image_name is documented as "Image name or ID." The description's "for an image" merely restates that the parameter scopes the query, adding 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?

"List member projects for an image" gives a specific verb (List) and resource (member projects) scoped to an image, so an agent knows exactly what it returns. It does not distinguish itself from siblings such as get_image_detail_list, so it falls 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 Guidelines2/5

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

The description offers no when-to-use guidance, no prerequisites, and never names an alternative. An agent cannot tell from this text whether this is the right tool for checking image sharing versus get_image_detail_list.

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