Red Hat Lightspeed MCP

Official

by RedHatInsights

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Show user's image blueprints (saved image templates/configurations for

image-builder__get_blueprints

Read-only

Retrieve saved image blueprints, including Linux distribution, package, and user configurations. Use this to list or search existing templates by name or paginate results.

Instructions

Show user's image blueprints (saved image templates/configurations for Linux distributions, packages, users).

🟢 CALL IMMEDIATELY - No information gathering required.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of items to return (use 7 as default)
`offset`	No	Number of items to skip when paging (use 0 as default)
`search_string`	No	Substring to search for in the name

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0May 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true. The description adds value by stating 'CALL IMMEDIATELY' and clarifying that no prior gathering is needed, which aligns with the read-only nature. No contradictions with annotations.

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?

The description is extremely concise with two sentences: first for purpose, second for usage hint. No redundant words; every sentence provides essential information.

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?

Given the presence of an output schema and annotations that cover read-only and open-world hints, the description fully covers what the tool does and when to use it. No gaps remain for this straightforward list tool.

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?

Input schema covers all 3 parameters with descriptions (100% coverage). The description does not add additional parameter semantics, so baseline score of 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 'Show user's image blueprints' with a specific verb and resource, and elaborates on content (saved templates/configurations for Linux distributions, packages, users). It distinguishes from sibling tools like image-builder__get_blueprint_details which focuses on a single blueprint.

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 includes '🟢 CALL IMMEDIATELY - No information gathering required', providing explicit guidance on when to use. However, it does not specify when not to use or compare to alternative tools for similar tasks.

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

Deploy Server