Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official
by RedHatInsights
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

List repositories with filtering and pagination options.

content-sources__list_repositories
Read-only

Find specific Red Hat repositories by applying filters for name, URL, architecture, version, origin, and more. Paginate results to control how many repositories are returned.

Instructions

List repositories with filtering and pagination options.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFilter by repository URL (case-insensitive).
archNoFilter by architecture (e.g., 'x86_64', 'aarch64').
nameNoFilter by repository name (case-insensitive).
limitNoMaximum number of repositories to return (default: 10, maximum: 100). **ALWAYS use the default value of 10 for the first call.** This default is carefully chosen for performance and context management. Only increase this value if the user explicitly asks to see more repositories at once.
offsetNoNumber of repositories to skip for pagination (default: 0).
originNoFilter by origin (e.g., 'red_hat', 'external').
enabledNoFilter by enabled status (True/False).
versionNoFilter by version (e.g., '8', '9').
content_typeNoFilter by content type (e.g., 'rpm', 'ostree').
include_gpg_keyNoInclude GPG key content in the response (default: False).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.0.10
    • addedInput schema / properties / include_gpg_key
      Added value: +{
+  "default": false,
+  "description": "Include GPG key content in the response (default: False).",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of repositories to return (default: 10)."New value: +"Maximum number of repositories to return (default: 10, maximum: 100). **ALWAYS use the default value of 10 for the first call.** This default is carefully chosen for performance and context management. Only increase this value if the user explicitly asks to see more repositories at once."
  2. First observedv0.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already cover the safety profile. The description adds a behavioral cue that no information gathering is needed, but it does not describe pagination behavior, response size, or any side effects. With annotations present, this is acceptable but not deeply transparent.

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?

The description is very short and front-loads the call-to-action. However, the first sentence only repeats the tool title/name, slightly wasting the opening line. Overall, it is efficient and avoids bulk.

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 tool has a rich input schema with 100% parameter coverage and an output schema exists, the description does not need to explain return values. It adequately introduces the tool's purpose and immediate-call guidance, but does not provide deeper context like common usage patterns or relationship to other tools.

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%, so each parameter is already documented with its meaning and default. The description adds only generic 'filtering and pagination' context beyond the schema, which is unnecessary but not harmful.

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 'List repositories with filtering and pagination options', identifying the specific verb, resource, and scope. It distinguishes itself from sibling tools, which target images, vulnerabilities, inventory, and RHSM, not content repositories.

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 explicitly says 'CALL IMMEDIATELY - No information gathering required,' giving clear guidance that no prerequisites are needed. It does not name alternatives or when-not-to-use, but among the siblings there is no competing repository-listing tool, so the context is sufficient.

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