Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official
by RedHatInsights
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get OpenAPI spec. Use this to get details e.g for a new blueprint

image-builder__get_openapi
Read-only

Fetch the Image Builder OpenAPI specification to discover endpoint details for blueprint creation or updates, optionally minimizing the spec to selected endpoints for payload preparation.

Instructions

Get OpenAPI spec. Use this to get details e.g for a new blueprint

šŸŸ¢ CALL IMMEDIATELY - No information gathering required.

Optional parameters:

  • endpoints: Comma-separated endpoint specs (like GET:/blueprints,POST:/blueprints). When provided, the returned OpenAPI is minimized to only the selected paths and their transitive component references. Use this only to prepare payloads for create_blueprint or update_blueprint.

Returns: OpenAPI specification JSON (possibly reduced when 'endpoints' is provided)

Raises: Exception: If the image-builder connection fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointsNoComma-separated list of endpoint specs to reduce the spec, e.g. 'GET:/blueprints,POST:/blueprints'. Only needed for create_blueprint/update_blueprint.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate readOnlyHint and openWorldHint, and the description adds context about returned JSON and potential exception. It does not contradict annotations.

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 description is somewhat verbose with emoji and optional parameter section, but purpose is front-loaded. Could be more concise.

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?

Given the output schema exists and annotations are present, the description is complete enough, covering return value, parameter usage, and error handling.

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%, but description adds value by explaining the purpose of the endpoints parameter (reducing spec to selected paths, transitive references) and linking to specific tools.

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 verb 'Get' and the resource 'OpenAPI spec', and distinguishes it from sibling tools that focus on other resources like blueprints or composes.

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

Usage Guidelines4/5

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

The description explains use cases (e.g., get details for a new blueprint) and when to use the optional endpoints parameter (for prepare payloads). It lacks explicit exclusions but provides clear context.

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

Deploy Server

Other Tools