Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

Get a list of all image builds (composes) with their UUIDs and basic status.

image-builder__get_composes
Read-only

Retrieve a list of image builds with UUIDs and status. Use this to find your build and get the UUID for detailed information.

Instructions

Get a list of all image builds (composes) with their UUIDs and basic status.

ALWAYS USE THIS FIRST when checking image build status or finding builds. This returns the UUID needed for get_compose_details. 🟢 CALL IMMEDIATELY - No information gathering required.

Common uses:

  • Check status of recent builds → call this first

  • Find your latest build → call this first

  • Get any build information → call this first Ask the user if they want to get more composes and adapt "offset" accordingly.

You can also provide this link so the user can check directly in the UI: https://console.redhat.com/insights/image-builder

Returns: List of composes with: - uuid: The unique identifier (REQUIRED for get_compose_details) - name: Blueprint name used - status: Current build status - created_at: When the build started

Example response: [ { "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "name": "my-rhel-image", "status": "RUNNING", "created_at": "2025-01-18T10:30:00Z" } ]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return (use 7 as default)
offsetNoNumber of items to skip when paging (use 0 as default)
search_stringNoSubstring to search for in the name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds behavior details: returns list with statuses, UUID needed for details, and no information gathering required. Provides example response.

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

Conciseness5/5

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

Well-structured with emphasis markers, bullet points, and example. Important information is front-loaded. Every sentence adds value.

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?

Covers all necessary aspects: what it returns, example, relationship to sibling tool, paging advice, and UI link. Complete for a listing tool with annotations.

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 covers all parameters with descriptions. The description adds usage guidance for offset but doesn't add meaning beyond schema descriptions. 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 clearly states the tool returns a list of all image builds (composes) with UUIDs and basic status. It differentiates from sibling tools like get_compose_details by noting that this returns the UUID needed for that tool.

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

Usage Guidelines5/5

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

Explicitly instructs 'ALWAYS USE THIS FIRST' and lists common scenarios (check status, find latest build). Also advises to ask user about offset for paging and provides a UI link.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RedHatInsights/insights-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server